commit-pr-flow
Finalizes implementation work with scoped commits and automated PR preparation.
Install
mkdir -p .claude/skills/commit-pr-flow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12810" && unzip -o skill.zip -d .claude/skills/commit-pr-flow && rm skill.zipInstalls to .claude/skills/commit-pr-flow
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.
Run a Phase C commit and PR flow from bounded plan items with strict scope control, validation gating, and review-ready output. Use when implementation is done and you need to stage intended files only, verify plan-to-diff alignment, create logical commits, and prepare or open a PR.Key capabilities
- →Confirm phase boundary for commit flow
- →Confirm scope boundary for changes
- →Run commit gate to check staged diff
- →Run validation gate with required checks
- →Create logical commits with clear messages
- →Prepare a pull request using a template
How it works
This skill enforces a Phase C commit and PR flow by confirming phase and scope boundaries, running commit and validation gates, creating logical commits, and preparing a pull request.
Inputs & outputs
When to use commit-pr-flow
- →Commit completed work
- →Create PR
- →Validate plan alignment
About commit-pr-flow
Enforces a Phase C workflow to ensure commits match plan items. Manages staging, validation, and PR creation while preventing scope creep.
Run a Phase C commit and PR flow from bounded plan items with strict scope control, validation gating, and review-ready output. Use when implementation is done and you need to stage intended files only, verify plan-to-diff alignment, create logical commits, and prepare or open a PR.
When not to use it
- →When requirement shaping is unresolved
- →When execution planning is unresolved
- →When staging all changes blindly
Limitations
- →Run only in Phase C
- →Does not replace agent/user judgment about scope changes
- →Does not claim readiness from command execution alone when scope or evidence gates are still ambiguous
How it compares
This workflow provides a strict, gated process for committing and creating pull requests, ensuring alignment with plan items and preventing scope creep, which is more controlled than a typical git workflow.
Compared to similar skills
commit-pr-flow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit-pr-flow (this skill) | 0 | 6mo | No flags | Advanced |
| resolve-conflicts | 81 | 12mo | Review | Intermediate |
| dependency-upgrade | 26 | 8mo | Review | Intermediate |
| git-commits | 21 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
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
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.