Skip to content

Railly/agent-brain / .agents/skills/ship

Commit, push, and optionally create PR

FileKindSize
SKILL.mdskill md651 B
---
name: ship
description: Commit, push, and optionally create PR
---

Ship current changes: $ARGUMENTS

1. Run `git status` to see changes
2. Run `git diff --stat` for overview
3. Stage relevant files (or all if no specific files mentioned)
4. Create commit with conventional format:
   - feat: new feature
   - fix: bug fix
   - docs: documentation
   - refactor: refactoring
   - chore: maintenance
5. Push to remote
6. If $ARGUMENTS contains "pr" or "--pr", create PR with `gh pr create`
7. Log to daily file: append `- [HH:MM] **shipped**: {commit message}` to `02_Journal/daily/YYYY-MM-DD.md`

Commit message format: `type(scope): description`
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall