agentleFS
7zrv7zrv/claude-code-monitor/.claude/skills/ship/SKILL.md

ship

Skill1 starsChanged 9 months agoMITView on GitHub

Stage, commit, push, and create a PR in one step

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    DO NOT proceed. Return immediately.

    line 43

“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 Changes (Commit + Push + PR)

Current State

  • Branch: !git branch --show-current
  • Status: !git status --short
  • Staged diff stat: !git diff --cached --stat
  • Unstaged diff stat: !git diff --stat
  • Recent commits: !git log --oneline -5
  • Commits vs main: !git log main..HEAD --oneline
  • Diff vs main stat: !git diff main..HEAD --stat
  • Remote tracking: !git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null || echo "no upstream"

Instructions

1. Main Branch 보호 확인

현재 브랜치가 main이면 즉시 중단하고 아래 메시지를 출력한다:

❌ Cannot ship directly from 'main' branch

All changes to 'main' must go through a Pull Request:

1. Create a feature branch:
   git checkout -b <type>/<name>-<issue-number>
   Example: git checkout -b feat/parse-history-2

2. Make your changes on the feature branch

3. Run /ship again from the feature branch

This protects main from direct commits per CONTRIBUTING.md rules.

DO NOT proceed. Return immediately.


2. Stage + Commit

커밋 규칙은 .claude/skills/shared/commit-conventions.md를 따른다. 해당 파일을 Read로 읽은 뒤 기준에 따라 커밋한다.

$ARGUMENTS가 제공되면 커밋 메시지 기반으로 사용한다.

3. Rebase + Push

PR 생성 규칙은 .claude/skills/shared/pr-template.md를 따른다. 해당 파일을 Read로 읽은 뒤, 1. 브랜치 최신화 및 2. 리모트 푸시 단계를 수행한다.

4. PR 생성

.claude/skills/shared/pr-template.md의 3~6 단계를 따라 PR을 생성한다.

추가 사항:

  • $ARGUMENTS에 이슈 번호가 있으면 해당 값을 사용한다
  • main 대비 모든 커밋을 분석하여 PR 내용을 작성한다

5. 결과 출력

✅ Ship 완료
- 커밋: <commit hash> <commit message>
- 브랜치: <branch> → origin/<branch>
- PR: <PR URL>

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.