Ship current changes: $ARGUMENTS
- Run
git statusto see changes - Run
git diff --statfor overview - Stage relevant files (or all if no specific files mentioned)
- Create commit with conventional format:
- feat: new feature
- fix: bug fix
- docs: documentation
- refactor: refactoring
- chore: maintenance
- Push to remote
- If $ARGUMENTS contains "pr" or "--pr", create PR with
gh pr create - Log to daily file: append
- [HH:MM] **shipped**: {commit message}to02_Journal/daily/YYYY-MM-DD.md
Commit message format: type(scope): description
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |