flutter/devtools · Archived

preparing-pr

Prepare a pull request by running presubmit with fixes. Use when preparing to commit or send a PR.

First seen Jun 20, 2026

Installation

$ npx skills add flutter/devtools --skill preparing-pr

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flutter/devtools.

npx skills add flutter/devtools

Browse all from flutter/devtools

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.7K
License LICENSE
Default branch master
Open issues 729
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,401 B
  • docs SUMMARY.md 118 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Preparing a Pull Request

Follow these steps to prepare a pull request for DevTools:

  1. Verify dt configuration:

- Ensure dt is available on the path by running dt --help or verifying its alias. - If not available, refer to the [CONTRIBUTING guide](../../../CONTRIBUTING.md#L64-L80) for instructions on how to set up the dt executable on your path.

  1. Update Flutter SDK:

- Run dt update-flutter-sdk to ensure the SDK is up to date.

  1. Run Presubmit with Fixes:

- Run dt presubmit --fix to address automated fixes. - If any issues remain or if the command fails, fix the issues manually and run dt presubmit --fix again to verify the fix.

  1. Run Tests for Affected Code:

- Use git status or git diff upstream/master to find changed files. - Run tests that are associated with the changed code. For example, if you edited packages/devtoolsapp/lib/src/screens/logging/loggingscreen.dart, run the logging tests under packages/devtools_app/test/screens/logging/.

Verification

If any step fails, stop and address the issue, and then verify the issue is fixed before proceeding.

[!IMPORTANT]
Do NOT commit or push changes without getting explicit user approval first.