agentleFS
DGouronDGouron/review-flow/.claude/skills/ship/SKILL.md

ship

Skill44 starsChanged 6 months agoMITView on GitHub

Ship — commit and push in one command. Chains quality gates, conventional commit, push, and optional PR creation + merge. Use when the user says "ship", "commit and push", "/ship", or wants to finalize a branch.

  • Reads credentials
  • Commits and pushes

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-sync, open-gstack-browser and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-sync

    Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

    Also in 6 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 10 projects that use this

  • ayudaySkill

    setup-deploy

    Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

    Also in 19 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 9 projects that use this

  • zebbernSkill

    debug-fix

    Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

    Also in 4 projects that use this

  • ramybarsoumSkill

    document-release

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.

    Also in 23 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    If branch = master: STOP — the protect-main-push.sh hook blocks push to master.

    line 47
  2. Distinctive:

    If nothing to commit: inform and stop.

    line 48
  3. Distinctive:

    If files are not staged, list them and add them by name (never git add -A or git add .)

    line 54
  4. Distinctive:

    ONLY if the user explicitly asked for merge: Never merge without explicit confirmation.

    line 141
  5. Very specific:

    NEVER: use --force push

    line 162
  6. Very specific:

    NEVER: use --no-verify or bypass hooks

    line 164
  7. Very specific:

    NEVER: commit .env, credentials, or secrets

    line 165
  8. Distinctive:

    ALWAYS: verify you are on a feature branch before pushing

    line 167

“Common” is measured: kept by at least 6 in 10 of the 181 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ship — Commit & Push

Activation

This skill activates with /ship. It chains verification, commit, push, and optionally PR creation and merge.

Optional arguments

/ship                   # Commit + push (no PR)
/ship pr                # Commit + push + gh pr create
/ship pr merge          # Commit + push + gh pr create + gh pr merge --admin --squash

Workflow

Step 0: Quality Gates (BLOCKING)

BEFORE any commit, run:

yarn verify

yarn verify runs: TypeScript check + Biome lint + Vitest tests.

If it fails: display the errors and STOP. Do not proceed until all quality gates pass.


Step 1: Analysis

git status --short
git branch --show-current
git log --oneline -5

Guards:

  • If branch = master: STOP — the protect-main-push.sh hook blocks push to master. Create a feature branch first.
  • If nothing to commit: inform and stop.

Step 2: Staging

  • If files are not staged, list them and add them by name (never git add -A or git add .)
  • NEVER include .env, credentials, secrets, or lock files unless explicitly requested
  • NEVER include files unrelated to the current change

Preferred pattern:

git add src/usecases/foo.usecase.ts src/tests/units/usecases/foo.usecase.test.ts

Step 3: Commit

Infer the message from the staged changes. Follow Conventional Commits:

<type>(<scope>): <description>
TypeUsage
featNew feature
fixBug fix
refactorRefactoring (no feature or fix)
testTests only
docsDocumentation only
choreMaintenance, dependencies
styleFormatting (no logic change)
perfPerformance improvement
ciCI/CD changes

Rules:

  • Header max 72 characters
  • Description in lowercase, no trailing period
  • Scope optional in parentheses, must match bounded context name when applicable

Commit via heredoc (preserves formatting):

git commit -m "$(cat <<'EOF'
feat(webhook): add GitHub signature validation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"

The pre-commit-gate.sh and verify-spec-updated.sh hooks run automatically. If they fail, fix the issue and retry — never use --no-verify.


Step 4: Push

git push -u origin <branch>

The protect-main-push.sh hook blocks push to master and force push. If it triggers, verify you are on a feature branch.


Step 5 (if pr or pr merge): Create PR

gh pr create --title "<type>(<scope>): <description>" --body "$(cat <<'EOF'
## Summary
- <bullet point 1>
- <bullet point 2>

## Test plan
- [ ] yarn verify passes
- [ ] Acceptance tests green

🤖 Generated with Claude Code
EOF
)"

Base branch: master.


Step 6 (if pr merge only and user explicitly requested): Merge PR

gh pr merge --admin --squash

ONLY if the user explicitly asked for merge. Never merge without explicit confirmation.


Step 7: Summary

SHIP

Branch  : <branch>
Commit  : <type>(<scope>): <description>
Push    : origin/<branch>
Gates   : yarn verify — green
PR      : <url or "not created">
Merge   : <squash merged or "not merged">

Security Rules

  • NEVER use --force push
  • NEVER push to master directly (hook enforces this)
  • NEVER use --no-verify or bypass hooks
  • NEVER commit .env, credentials, or secrets
  • NEVER stage with git add -A or git add .
  • ALWAYS verify you are on a feature branch before pushing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.