Axidify Pull request
Run review (three passes; and test if not already) before opening when changes are substantive. Use security or performance when those risks dominate.
Checklist
- Branch state —
git status; branch tracks remote; commits ahead of base - Base branch — confirm
main/developper project convention - Diff scope —
git diff [base]...HEAD; summarize all commits on the branch - Push — only if the user explicitly asked (
git push -u origin HEAD), or when this skill runs as release Phase 0 - Create PR — use
gh pr createwhen GitHub is the host
PR body (adapt to project template if one exists)
## Summary
- …
## Test plan
- [ ] …
Rules
- NEVER update git config
- Do not force-push
main/masterwithout explicit user request and warning - Return the PR URL when created
- Link related issues (
Fixes #123) when the user provides IDs
release owns the full ship sequence: this skill (Phase 0) → merge → version/tag. When the user says release, do not stop after opening the PR.
User shorthand (with release)
| User says | Agent does |
|---|---|
| go | This skill — open PR only |
| merge | Merge PR + sync main (release Phase A) |
| release / ship | release Phase 0 → A → B (PR, merge, then release) |
| merge and release | release Phase A → B (Phase 0 if no PR yet) |
Related skills
- review — run before opening
- test — evidence for test plan
- ci — fix red checks before or after PR
- release — after PR: merge + version/tag when user asks to ship
- plan-driven-implementation — update plan Progress/Issues logs when PR implements
docs/plans/