agentleFS
krishnamallamkrishnamallam/upbox/.claude/skills/ship/SKILL.md

ship

Skill2 starsChanged 6 months agoMITView on GitHub

Scan changes, commit, push, and create a PR. With confirmation at each step

  • Reads credentials
  • Commits and pushes

194 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-sync, open-gstack-browser and 9 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

  • 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

  • ShreyRaviSkill

    setup-gbrain

    Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)

    Also in 7 projects that use this

  • +1 more from ShreyRavi

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 0 are common, 14 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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. Distinctive:

    Run git status to see all changed, staged, and untracked files

    line 23
  2. Distinctive:

    Run git diff to see what changed (staged + unstaged)

    line 24
  3. Distinctive:

    Run git log --oneline -5 to see recent commit style

    line 25
  4. Distinctive:

    If there are no changes, tell the user and stop

    line 31
  5. Distinctive:

    Only after confirmation: stage the files and create the commit

    line 44
  6. Distinctive:

    If the commit fails (e.g., pre-commit hook), fix the issue and try again with a NEW commit

    line 45
  7. Distinctive:

    Check if the current branch has an upstream remote

    line 49
  8. Very specific:

    If not, propose creating one with git push -u origin <branch>

    line 50
  9. Distinctive:

    ASK the user to confirm: before pushing

    line 51
  10. Distinctive:

    Only after confirmation: push to remote

    line 52
  11. Very specific:

    Check if a PR already exists for this branch (gh pr view.

    line 56
  12. Distinctive:

    Test plan: how to verify

    line 60
  13. Very specific:

    Only after confirmation: create the PR with gh pr create

    line 62
  14. Distinctive:

    NEVER skip a confirmation step.

    line 67
  15. Distinctive:

    NEVER commit .env, secrets, or credential files

    line 69
  16. Distinctive:

    If the user says "skip" at any step, skip that step and move to the next

    line 70
  17. Distinctive:

    If $ARGUMENTS is provided, use it as the commit message / PR title

    line 71

“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 the current changes through commit, push, and PR creation. Confirm with the user before each step using the AskUserQuestion tool.

Step 1: Scan

  • Run git status to see all changed, staged, and untracked files
  • Run git diff to see what changed (staged + unstaged)
  • Run git log --oneline -5 to see recent commit style
  • Present a clear summary to the user:
    • Files modified
    • Files added
    • Files deleted
    • Untracked files
  • If there are no changes, tell the user and stop

Step 2: Stage & Commit

  • Propose which files to stage. Never stage these:
    • Secrets: .env*, *.pem, *.key, credentials.json
    • Lock files: package-lock.json, yarn.lock, pnpm-lock.yaml (unless intentionally updated)
    • Generated: *.gen.ts, *.generated.*, *.min.js, *.min.css
    • Build output: dist/, build/, .next/, __pycache__/
    • Dependencies: node_modules/, vendor/, .venv/
    • OS/editor: .DS_Store, Thumbs.db, *.swp, .idea/, .vscode/settings.json
  • Draft a commit message based on the changes, matching the repo's existing commit style
  • ASK the user to confirm or edit: show the exact files to stage and the proposed commit message
  • Only after confirmation: stage the files and create the commit
  • If the commit fails (e.g., pre-commit hook), fix the issue and try again with a NEW commit

Step 3: Push

  • Check if the current branch has an upstream remote
  • If not, propose creating one with git push -u origin <branch>
  • ASK the user to confirm before pushing
  • Only after confirmation: push to remote

Step 4: Pull Request

  • Check if a PR already exists for this branch (gh pr view. If it exists, show the URL and stop)
  • Analyze ALL commits on this branch vs the base branch (not just the latest commit)
  • Draft a PR title (under 72 chars) and body with:
    • Summary: 2-4 bullet points
    • Test plan: how to verify
  • ASK the user to confirm or edit the title and body
  • Only after confirmation: create the PR with gh pr create
  • Show the PR URL when done

Rules

  • NEVER skip a confirmation step. Each step requires explicit user approval
  • NEVER force-push
  • NEVER commit .env, secrets, or credential files
  • If the user says "skip" at any step, skip that step and move to the next
  • If $ARGUMENTS is provided, use it as the commit message / PR title

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.