Guides commit, push, and draft PR creation for stories. Use when ready to commit changes, pushing to remote, or creating a pull request for review.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Acceptance testing can occur at different points depending on team workflow:
| Workflow | When to Accept |
|---|---|
| Pre-commit | Developer verification → PO accepts → Commit |
| Pre-push | Commit locally → PO accepts → Push |
| Post-PR | Commit → Push → Draft PR → PO accepts → Ready for review |
Choose based on:
Before Commit:
- [ ] Developer verification complete
- [ ] All tests pass
- [ ] Linting passes
- [ ] Story log updated with completed work
Use Conventional Commits format:
<type>(<scope>): <summary>
<body explaining why this change is necessary>
Types: feat, fix, refactor, test, docs, chore
Example:
feat(sync): implement workspace Git initialization
Enable users to sync their notes to GitHub by
initializing the workspace as a Git repository.
Guidelines:
git push -u origin <branch-name>
For post-PR acceptance workflow:
gh pr create --draft --title "<title>" --body "$(cat <<'EOF'
## Summary
- [Key change 1]
- [Key change 2]
## Story
[Link to story log if applicable]
## Test Plan
- [How to verify this works]
**Status: Awaiting acceptance testing**
EOF
)"
Mark as ready after acceptance:
gh pr ready
After product owner accepts: