ship-feature
Skill682 starsChanged 5 days agoMITView on GitHub
Use when starting work, committing or opening a PR — "start a new feature", "commit this", "what branch should this target". Covers branch naming, conventional commits and the dev-to-main squash-merge release flow.
- Commits and pushes
16 other projects use a version of this.
Adopted by
Most recently taken up by
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- seanmcgary/claude-skillstheir own version, first seen Nov 11, 2026
- babs/skillstheir own version, first seen Nov 8, 2026
- azents/azentstheir own version, first seen Oct 23, 2026
- mergewatch/mergewatch.aitheir own version, first seen Oct 18, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- classroomio/classroomio★ 1.7ksame name
- hoangsonww/Claude-Code-Agent-Monitor★ 1.2ksame name
- ultimo-rs/ultimo★ 777same name
- theexperiencecompany/gaia★ 327same name
- seldonframe/seldonframe★ 40same name
- mergewatch/mergewatch.ai★ 26same name
- azents/azents★ 16same name
- shubham303/meelu-analytics-mcp★ 9same name
- babs/skills★ 4same name
- FAHTHIZ/oasis★ 4same name
6 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-system-actionSkill
- chezmoi-scriptsSkill
- docs-siteSkill
- fork-and-customizeSkill
- run-testsSkill
- vm-labSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
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
- Very specific: line 17
All work branches off dev and is named feature/<name> or bugfix/<name>.
- Very specific: line 19
After a stable release, merge main back into dev.
- Very specific: line 45
Use make test-local ARGS="..." for focused debugging.
- Very specific: line 47
If the branch is behind dev: git merge dev (if already pushed) or git rebase dev (if only local).
- Distinctive: line 56
Run these only on disposable CI hosts.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Shipping a change in personal-os-setup
This repo drives releases from commit messages via python-semantic-release, so the branch/PR/commit conventions are load-bearing, not stylistic.
⚠️ Commit and push each need their own approval. Nothing here is pre-approved: ask per action, even if the user already asked for the feature. git push, merging and anything touching main/release branches need the same per-action yes. If a confirmation prompt times out, stop — silence is not consent. Canon: AGENTS.md § "Safety: confirm before system-mutating actions (MANDATORY)".
Branching
- All work branches off
devand is namedfeature/<name>orbugfix/<name>. - Feature PRs target
devfor release candidates; promotedevtomainfor stable releases. - After a stable release, merge
mainback intodev; keep stable version/changelog metadata and regenerateuv.lock. Commit and push each require approval. git checkout dev && git pullbefore branching, to start from a fast-forward-clean base.
Commit messages
Conventional Commits, gitmoji prefix optional: [emoji] <type>[(<scope>)][!]: <description>.
| type | release bump |
fix, perf | patch |
feat | minor |
feat! / BREAKING CHANGE: footer | major |
chore, ci, docs, style, refactor, test, build | no release |
Examples: ✨ feat(auth): add GitHub App token rotation, 🐛 fix(llm): handle null response from API.
Full type/emoji table and scopes: docs/developer/3.conventions.md, “Commit convention”.
Never manually bump the version in pyproject.toml — semantic-release does it on merge. Never create tags manually.
⚠️ commitizen's commit-message check only runs at git's commit-msg hook stage — make pre-commit does not exercise it, so a passing make pre-commit says nothing about whether your commit message is well-formed; only a real git commit does. See [[run-tests]].
Before opening a PR
make check— static/docs hooks, full safe unit/skills suites and artifact/runtime checks. Dependencies/hooks must already be installed. For new files, pass explicit paths throughFILES="<paths>"; the default covers tracked files.- Use
make test-local ARGS="..."for focused debugging. Full validation targets rejectARGSandPYTEST_ADDOPTS. See [[run-tests]] for isolation and platform boundaries. - If the branch is behind
dev:git merge dev(if already pushed) orgit rebase dev(if only local). Re-runmake checkafter syncing.
Opening the PR
- Target
devfor features/fixes;mainfor the stable promotion fromdev. - The PR title must follow the commit convention (e.g.
feat: add new plugin) — all PRs squash-merge, and the PR title becomes the commit message semantic-release evaluates. - CI (
ci.yml→quality-and-tests.yml) runs static checks and full safe suites plus platform integration. Linux/macOS integration installs real packages; Windows integration is read-only. Run these only on disposable CI hosts. A local pass does not establish hosted CI success.
What happens after merge
- Merging to
main→🚀 Release — Main / Devruns semantic-release: it bumps the version from the conventional commit(s), tags, cuts the GitHub Release if the merged commits were releasable, and deploys docs only if a release actually happened (an all-docs:/chore:PR triggers neither — see [[docs-site]]). A non-releasable merge is a normal outcome, not a failure. - Merging releasable changes to
devpublishes anrcprerelease without deploying docs. GitHub Actions automatically binds both release branches to the testedGITHUB_SHA. Locally, runmake releasefrom clean, synchronizedmainordev; it usesHEAD. Both paths verify artifacts before publication and resume interrupted uploads.
Branch/PR flow: docs/developer/3.conventions.md, “Branches and pull requests”.
For test conventions specific to frontend/factory code (never invoke real package managers from a test), see [[add-system-action]] and [[run-tests]].
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.

