commit-push-deploylisted

The whole way out of a working tree — documentation, tests, one commit, the push to GitHub, and, when it is a release, the tag that publishes k0 to npm. Use this skill whenever the user asks for the work to be shipped, in whatever words and whatever language — "commit and push", "ship it", "cut a release", "publish", "committa e pusha", "manda in produzione", "fai una release", "/commit-push-deploy". It calls the changelog skill rather than repeating it, runs the tests and the coverage floor before anything leaves the machine, watches the run on GitHub, and stops to ask exactly once, before the tag that cannot be taken back. Do not use it to write a commit message on its own, to inspect what changed, or when the user only wants the changelog.
alessio-ragni/k0-board · ★ 1 · Code & Development · score 74

Install: claude install-skill alessio-ragni/k0-board

# Getting the work out There is one road out of this repository and this is it: documentation, tests, one commit, a push to `origin`, and — only when a release was asked for — a tag whose arrival on GitHub is what publishes k0 to npm. The point of writing it down is that the order matters and the last step is irreversible. A version that reaches the registry cannot be taken back; it can only be followed by another one, in public, for ever. ## What this skill does not do - **It does not write the changelog or the documentation.** That is the `changelog` skill, and it owns `README.md`, `docs/database.md`, `docs/testing.md` and `CHANGELOG.md`, along with the rules about how an entry reads. Invoke it and follow it. Do not restate its rules here and do not second-guess them. - **It never types `npm publish`.** Publishing is what the tag causes; see *The release*. - **It never pushes to `private`.** See *The two remotes*. - **It never installs anything.** k0 has no dependencies and no lockfile. There is no `npm ci` step, and adding one is a change to the project, not a step in a release. ## The stack it stands on | What | Which | |---|---| | The commit and the tag | `git`, Conventional Commits, one line, imperative, English | | The tests | `npm test` — Node's own test runner, no framework, no dependency | | The coverage floor | `node --test --experimental-test-coverage`, the numbers living in `.github/workflows/ci.yml` | | Watching the run | the `gh` CLI, already auth