github-pr-workflow Skill
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments. Published by microsoft in amplifier-app-paperclip.
Decision snapshot
Is this a fit?
Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is github-pr-workflow Skill?
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments. Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Declared skill metadata
- Source file: packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use github-pr-workflow Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: packages/skills-catalog/catalog/bundled/software-development/github-pr-workflow/SKILL.md
What it does
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
Skill instructions
GitHub Pull Request Workflow Ship a PR a reviewer can land without follow-up clarifying questions. The aim is high signal in the title and body, evidence the change works, and clean replies when feedback comes in. When to use - You are about to open a PR for a change that is functionally complete. - A reviewer left comments and you need to respond and push fixes. - A PR has been open more than a day and needs to be brought back into shape (stale conflicts, missing description, missing verification). When not to use - The change is not yet functionally complete. Finish the work first; draft PRs that bounce on review are noise. - The repository uses a non-GitHub forge. Adjust to that forge's conventions; do not force GitHub-isms. Branch hygiene before opening - Rebase or merge from the target base so the diff is current. - Squash WIP commits into reviewable units. Prefer one commit per logical change; do not force one-commit-per-PR if the work is genuinely multi-step. - Confirm tests, ty
Verified compatibility and discovery
Frequently asked questions
What is github-pr-workflow?
github-pr-workflow is a open-source AI agent skill with Copy skill directory. Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
Who is github-pr-workflow best for?
github-pr-workflow is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install github-pr-workflow?
Install or run github-pr-workflow using Copy skill directory. Check github-pr-workflow for the latest setup command.
Is github-pr-workflow actively maintained?
github-pr-workflow may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
