agentleFS
Sign inStart free
nortonxnortonx/ai-tooling-free/skills/ship-it/SKILL.md

ship-it

Skill1 starsChanged 2 months agoMITView on GitHub

Branch (if needed), commit, and push the current changes to remote in one step. Invoke only when the user explicitly runs /ship-it or asks to branch-commit-push, it reminds you to review first, then commits and pushes. Args: [<branch-name-or-card>]

  • Commits and pushes

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use modern-go, loop-it 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.
  • jidechaoSkill

    modern-go

    Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.

    Also in 3 projects that use this

  • jidechaoSkill

    loop-it

    Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 5 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 4 projects that use this

  • GoogleSkill

    to-issues

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    Also in 3 projects that use this

  • Hugging FaceSkill

    simplify

    Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

    Also in 3 projects that use this

  • +2 more from jidechao

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 42 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:

    If the push is rejected (remote ahead, protected branch, etc.), stop and report the error verbatim.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 42 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 it

⚠️ Review the changes first. Show the working-tree status and the commit message you are about to use, and confirm the changes are what is intended: this stages everything, commits, and pushes to remote. Running /ship-it is the user explicit authorization to commit and push for this run (it waives the usual "ask before committing/pushing" rule for this invocation only).

Arguments

[branch-name-or-issue-id]: optional. Overrides the branch name only; the commit message is always auto-derived from the diff.

  • A full branch name (feat/checkout-retry) is used verbatim.
  • A bare issue/ticket id (123) becomes <type>/<issue-id>-<slug>.
  • Omitted -> <type>/<slug> derived from the diff.

(Copilot CLI and skills do not substitute $ARGUMENTS; include the branch name or issue id inline in your prompt when you want to override.)

Steps

  1. Gather context: run:
    git branch --show-current
git status --short
git diff --stat HEAD
git log --oneline -10
    Resolve the default branch: git symbolic-ref --quiet --short refs/remotes/origin/HEAD (strip the origin/ prefix); fall back to main, else master.
  2. If the working tree is clean, stop and say "nothing to ship". Do nothing else.
  3. Branch:
    • On the default branch (main/master) -> create and switch to a new branch (git switch -c <name>). Name it from the argument if given, else derive <type>/<slug>, where <type> in feat|fix|refactor|docs|test|chore|perf|ci, <slug> = short kebab summary of the change. An issue-id argument like 123 -> <type>/<issue-id>-<slug>.
    • On a feature branch already -> reuse it; do not create another.
  4. Stage everything: git add -A.
  5. Commit following the create-commit-message convention: <type>: <imperative summary, <=72 chars>; reference the issue id from the branch name when present (e.g. (#123) suffix). Focus the summary on the why. One commit only; do not split. Single quotes only if quoting.
  6. Push with upstream tracking: git push -u origin HEAD.
  7. Report in 2 to 3 lines: branch name, commit subject, and push result (include any PR-create hint git prints).

Rules

  • Never force-push, amend, rebase, or touch any branch other than the one being shipped.
  • If the push is rejected (remote ahead, protected branch, etc.), stop and report the error verbatim; do not rebase, pull, or force to recover.
  • Invoke only on explicit user request; never auto-trigger a commit or push.

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.

Check your setup, free