ship-it
Skill2 starsChanged 19 days agoMITView on GitHub
Releases main, with or without a milestone: reads the commits and CHANGELOG `[Unreleased]` entries since the last release, proposes the next version in the last release's scheme (`0.x`, CalVer `YY.MM.MICRO` or SemVer), bumps each version file and moves the entries under the new version in one MR, then tags its merge commit, asking first unless the version came as its argument. Use when the user asks to "cut a release", "release main", "ship 26.11", "ship it" or "bump the version".
49 other projects use a version of this.
Adopted by
Most recently taken up by
- avinashankur/skillstheir own version, first seen Nov 15, 2026
- arvmaan/skillstheir own version, first seen Nov 15, 2026
- alexandrosandre/agentic-engineeringtheir own version, first seen Nov 8, 2026
- alexandrosandre/alice-issue-agenttheir own version, first seen Nov 8, 2026
- spencerldixon/skillstheir own version, first seen Nov 8, 2026
- unional/skillstheir own version, first seen Nov 6, 2026
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.
jidechaoSkillmodern-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
jidechaoSkillloop-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
SentrySkillcreate-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
GitHubSkillrefactor
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
GoogleSkillto-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 FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 3 projects that use this
- +2 more from jidechao
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- vectorize-io/hindsight★ 61ksame name
- learntocloud/learn-to-cloud-app★ 1.1ksame name
- leonvanzyl/agentic-coding-starter-kit★ 447same name
- smallnest/goal-workflow★ 283same name
- frappe/skills★ 169same name
- DECRUX9812/hermes-plugin-gameforge★ 44same name
- awslabs/llm-evaluation-system★ 27same name
- LunkiBR/ship-it★ 18same name
- paultyng/skill-issue★ 8same name
- davidmeirlevy/obvious-skills★ 6same name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-teamSkill
- assemble-metaSkill
- brainstormSkill
- build-issueSkill
- cut-milestonesSkill
- frictionSkill
- milestone-closeSkill
- qa-reviewSkill
- review-benchSkill
- scope-commitSkill
- scope-issueSkill
- scope-mrSkill
- scope-specSkill
- setup-dream-teamSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
0
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
- Very specific: line 19
Read the commits on main since the last release and the CHANGELOG [Unreleased] entries.
- Very specific: line 22
No tag and no version file → 0.1.0.
- Very specific: line 29
No version file or no CHANGELOG [Unreleased] entries → say so in the proposal.
“Common” is measured: kept by at least 6 in 10 of the 45 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.
Files
ship-it
1. Propose
- Last release: the newest
v*tag on main; no tag → the last commit that changed the version file. - Read the commits on main since the last release and the CHANGELOG
[Unreleased]entries. - Propose the next version from the last release's version, its tag or else the version file;
the user approves it, names another version or declines:
- No tag and no version file →
0.1.0. - A
0.xversion → the next minor:v0.4.0→0.5.0. - A CalVer
YY.MM.MICROversion → this month'sYY.MM, MICRO one above the last release's in the same month, else 0:v26.11.0→26.11.1in November 2026,26.12.0in December. - A CalVer month has no leading zero:
27.5.0, never27.05.0. - A SemVer version at
1.0or above → the next minor, unless the user names a CalVer version.
- No tag and no version file →
- A version passed as the skill argument → that version is the release; don't wait for a reply.
- No version file or no CHANGELOG
[Unreleased]entries → say so in the proposal; create neither. - The project's
CLAUDE.mdorAGENTS.mdforbids tagging → the Tag: line readsnone, <that file> forbids tagging. - Lay out the proposal as:
- **Version:** <current> → <next>
- **Commits:** <n> since <last tag or version commit>
- **CHANGELOG:** <n> `[Unreleased]` entries move under `[<next>] - <date>`
- **Tag:** `v<next>` on the MR's merge commit, <pushed | offered> once it merges- Tagging not forbidden → the Tag: line reads
pushedwhen the version came as the skill argument, elseoffered.
2. Bump
- One MR: bump each version file, rename the CHANGELOG
[Unreleased]to[<version>] - <date>and add an empty[Unreleased]above it.
3. Tag
CLAUDE.mdorAGENTS.mdforbids tagging → no tag; this wins over the two lines below.- Once that MR merges and the version came as the skill argument → create and push a
v<version>tag on its merge commit without asking. - Once that MR merges and the version came any other way → offer a
v<version>tag on its merge commit.
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
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.

