pr-closeout
Guides the final steps of a task, including verification, PR creation, and updating project documentation.
Install
mkdir -p .claude/skills/pr-closeout && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10308" && unzip -o skill.zip -d .claude/skills/pr-closeout && rm skill.zipInstalls to .claude/skills/pr-closeout
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this guidance when finishing a feature branch, tracked plan item, or any task that is expected to end in a GitHub pull request.Key capabilities
- →Open non-draft PR
- →Write detailed PR body
- →Assign labels and milestones
- →Validate branch changes
How it works
It ensures feature branches are finalized with detailed PR descriptions and proper metadata.
Inputs & outputs
When to use pr-closeout
- →Open a PR for a completed task
- →Validate branch changes before pushing
- →Update planning documents post-merge
- →Assign labels and milestones to a PR
About this skill
PR Closeout Skill
Use this guidance when finishing a feature branch, tracked plan item, or any task that is expected to end in a GitHub pull request.
Completion Rule
- Work is not complete until a non-draft PR is open on GitHub.
- The PR must target
mainunless the task explicitly says otherwise. - The PR must have a detailed description that is ready for human review.
- The PR must have appropriate labels and an assigned GitHub milestone.
Preferred Tooling
- Use the repo-specific GitHub MCP first for repository reads and GitHub mutations when the needed capability exists.
- Use the repo-specific Git MCP first for local git actions when available.
- Fall back to
ghor localgitonly for capabilities the MCP path does not expose cleanly.
Required Closeout Steps
- Confirm the branch contains only the intended scope.
- Run the narrowest relevant validation for the touched files.
- Stage and commit the intended changes.
- Push the branch to
origin. - Open a non-draft PR against
main. - Write a detailed PR body covering:
- what changed
- why it changed
- user or operator impact
- validation performed
- Apply appropriate labels for the workstream or tracked plan item.
- Assign the PR to the relevant GitHub milestone.
- If the needed label or milestone does not exist, create it before finishing.
- Update any checked-in planning or agent-context files that should describe the post-merge state.
- Run
python scripts/validate_agent_plan.pybefore opening the PR if.agent-plan.mdchanged.
Repo-Specific Expectations
- For tracked plan work, keep
.agent-plan.md,README.md, and relevant human-facing planning docs aligned with the PR's expected post-merge state. - Rewrite
.agent-plan.mdas post-merge mainline truth rather than branch-local progress notes. - Keep
.agent-plan.mdin the validated format: required headings, exact mainline status fields, and exactly one[next]item. - Do not treat a local branch, a pushed branch, or a draft PR as the terminal state.
- If GitHub publication is blocked, report the blocker explicitly; do not claim the task is complete.
When not to use it
- →Draft PRs
- →Projects without GitHub
Prerequisites
Limitations
- →Requires GitHub
- →Must target main
How it compares
It mandates validation and alignment of project planning files before merging.
Compared to similar skills
pr-closeout side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr-closeout (this skill) | 0 | 3mo | No flags | Beginner |
| triage-helper | 1 | 6mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
triage-helper
flutter
Assistance with triage of unprioritized issues. Use when the user asks for help with triage.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration