OpenParable
Skip to content
← Back to skills

Preparing PR

Development
preparing-pr

Preparing PR is an Agent Skill for development published in the flutter/devtools repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/flutter/devtools/blob/HEAD/.agents/skills/preparing-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/preparing-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 for instructions on how to set up the dt executable on your path.
  2. Update Flutter SDK:
    • Run dt update-flutter-sdk to ensure the SDK is up to date.
  3. 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.
  4. 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/devtools_app/lib/src/screens/logging/logging_screen.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.