Fast Pull Request Agent Skill
Generate a pull request description for the FAST repository using the provided template.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/microsoft/fast --skill fast-pull-requestThe instruction itself
as written by the authorThis skill only applies to generating Pull Request descriptions for the FAST repository.
Do not create or modify any existing Github pull requests. This skill is only for
generating the markdown content for a pull request description based on the provided template.
Based on the conversation context, generate a pull request description as a markdown code
block using the template located at
../../pull_request_template.md.
Use the Pull Request Template to generate a markdown code block for the most
relevant work on this git branch, compared to main.
The Description should be either a summary description of the content of the branch,
or a list of the most relevant changes made in the branch. The goal is to address
the purpose of the pull request in a concise manner, rather than detailing every change. "Why"
and "what" over "how".
Determine if any current github issues are being addressed by this work, and
list them in the Issues section with links. If none are found, remove the Issues section.
The reviewer notes section is optional. Include it only if there are specific
areas where you would like feedback or attention from the reviewer.
The Test Plan section should outline any issues that need to be verified before merging,
or steps to reproduce the behavior locally. Even a brief note is helpful, such as "All existing tests pass".
The checklist section should be completed to indicate the status of various
aspects of the pull request.
If there are change files that have been added to the PR, check the box labeled "I have included a change request file using $ npm run change".
If any new tests have been added, check the box labeled "I have added tests for my changes."
Check the terminal output for evidence of passing tests, and check the box labeled "I have tested my changes." if tests have been run and are passing. If not, leave the box unchecked.
If any doc blocks have been added or modified, or if any documentation files have been added or modified, check the box labeled "I have updated the project documentation to reflect my changes." This also applies to any changes made to api-report files.
The final checkbox must be checked by the pull request author. It should never be checked when generating this PR description.
The Next Steps section is optional. Include it only if there are specific follow-up tasks
or work items that should be addressed after merging this PR, such as updating documentation, adding new tests, or performing code cleanup. If any existing issues are being addressed by the next steps, reference them here.
Provide the markdown code block only, without any additional commentary or explanation.
Any comments in the template can be removed since they're only meant to provide
guidance on how to fill out the template, and are not intended to be part of the
final PR description.
Other skills for the same job
different authors, same section of the catalogue
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
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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
Comprehensive GitHub code review with AI-powered swarm coordination
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.
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.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
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.
How to use it
Take microsoft/fast-pull-request from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.