mcpbeat Sign in

Preparing Pr Agent Skill

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

350 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1727
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/flutter/devtools --skill preparing-pr

The instruction itself

2 sections, as written by the author

Preparing a Pull Request

Follow these steps to prepare a pull request for DevTools:

  • 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.
  • Update Flutter SDK:
  • Run dt update-flutter-sdk to ensure the SDK is up to date.
  • 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.
  • 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.

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take flutter/preparing-pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.