What problem does it solve? Automated bots often create messy pull requests by bundling unrelated changes, staging internal management files, or losing track of existing PR branches. This Skill standardizes how an AI agent stages changes, writes PR descriptions, and continues work on existing PRs. ## Core Features & Use Cases - Surgical Change Staging: Enforces one fix per PR and explicitly stages only relevant files with git add, while forbidding internal bot files like pr-description.md or branch-name.txt from being committed. - PR Description Generation: Creates pr-description.md with a conventional title on the first line and a markdown body explaining the change and its impact. - Existing PR Recovery: Tracks branch names and PR IDs via branch-name.txt and pr-number.txt, writes maintainer responses to issue-comment.md or pr-comment.md, and diagnoses CI failures with gh run view. - Use Case: A bot fixing a failing CI check on its own PR can regenerate the patch, stage only the fix, and reply to reviewer feedback without polluting the commit with internal state files. ## Quick Start Use the prs skill to stage my fix, generate a PR description, and update the existing pull request with a response to the reviewer comment.