agentleFS
AmineDjeghriAmineDjeghri/awesome-os-setup/.claude/skills/ship-feature/SKILL.md

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

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
  1. Very specific:

    All work branches off dev and is named feature/<name> or bugfix/<name>.

    line 17
  2. Very specific:

    After a stable release, merge main back into dev.

    line 19
  3. Very specific:

    Use make test-local ARGS="..." for focused debugging.

    line 45
  4. Very specific:

    If the branch is behind dev: git merge dev (if already pushed) or git rebase dev (if only local).

    line 47
  5. Distinctive:

    Run these only on disposable CI hosts.

    line 56

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 dev and is named feature/<name> or bugfix/<name>.
  • Feature PRs target dev for release candidates; promote dev to main for stable releases.
  • After a stable release, merge main back into dev; keep stable version/changelog metadata and regenerate uv.lock. Commit and push each require approval.
  • git checkout dev && git pull before branching, to start from a fast-forward-clean base.

Commit messages

Conventional Commits, gitmoji prefix optional: [emoji] <type>[(<scope>)][!]: <description>.

typerelease bump
fix, perfpatch
featminor
feat! / BREAKING CHANGE: footermajor
chore, ci, docs, style, refactor, test, buildno 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

  1. 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 through FILES="<paths>"; the default covers tracked files.
  2. Use make test-local ARGS="..." for focused debugging. Full validation targets reject ARGS and PYTEST_ADDOPTS. See [[run-tests]] for isolation and platform boundaries.
  3. If the branch is behind dev: git merge dev (if already pushed) or git rebase dev (if only local). Re-run make check after syncing.

Opening the PR

  • Target dev for features/fixes; main for the stable promotion from dev.
  • 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 / Dev runs 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 dev publishes an rc prerelease without deploying docs. GitHub Actions automatically binds both release branches to the tested GITHUB_SHA. Locally, run make release from clean, synchronized main or dev; it uses HEAD. 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]].

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.