/cf-ship

Context footprint: ⚡ (low) — what does this mean?

The /cf-ship skill automates the final steps of feature delivery: verifying tests and build, creating a conventional commit, pushing to remote, and opening a pull request.

Usage

/cf-ship [hint]
/cf-ship --dry-run    # Preview without pushing or creating PR

What It Does

1. Verifies — Runs the full cf-verification checklist (tests, build, linter) — stops and fixes if anything fails
2. Commits — If there are uncommitted changes, runs the /cf-commit workflow using your hint
3. Pushes — Pushes the branch to origin — if the remote is ahead, rebases first then retries
4. Creates PR — Opens a pull request via gh CLI if on a feature branch. If on main/master, warns and skips. PR title uses conventional commit style (under 70 chars). Falls back to a manual link if gh is not installed
5. Reports — Shows the commit SHA, push result, and PR URL

Examples

/cf-ship Add notification system

Output:

✓ Tests passed (42 passed, 0 failed)
✓ Commit created: feat: add notification system with email and SMS
✓ Pushed to origin/feature/notification-system
✓ PR created: https://github.com/yourorg/repo/pull/42

/cf-ship
# Automatically generates commit message and ships

PR Body

The generated PR includes:

## Summary

- 1-3 bullet points describing the changes

## Test plan

- [ ] Tests pass
- [ ] Manual verification done

Dry-Run Mode

Use --dry-run to preview the entire workflow without any side effects:

/cf-ship --dry-run

Each step shows what would happen (prefixed with [dry-run]) — no commit is created, nothing is pushed, and no PR is opened. Useful for verifying the workflow before shipping.

Rules

• Never force pushes unless explicitly asked
• Never pushes to main/master directly
• Always verifies before pushing
• Asks before pushing if there are concerns
• No AI attribution in commits or PRs

When to Use

• Ready to ship a completed feature
• Bug fix tested and verified
• Documentation updates finalized
• Any work ready for team review

Workflow Integration

/cf-plan → implement → /cf-review → /cf-commit (loop) → /cf-ship

💡 You should extend this skill with Custom Skill Guides to add additional steps before or after the standard workflow. See Custom Skill Guides for more details.