drwil-release
Post a Git tag and a GitHub release note on the latest merged workstream (optional module, never modifies a tracked file). Use once the module is activated on the project, to preview (--dry-run) then create the release.
- License 许可
- MIT
- 所属仓库
- wdubilly/drwil
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- drwil-release
- description
- Post a Git tag and a GitHub release note on the latest merged workstream (optional module, never modifies a tracked file). Use once the module is activated on the project, to preview (--dry-run) then create the release.
03 SKILL.md 正文
Recipe: docs/recipes/create-a-release.md. Optional module, not
installed by default — first check that .githooks/create-release.mjs (if present) exists
(otherwise follow the activation steps described in
the recipe before continuing). Always start with
node .githooks/create-release.mjs --dry-run and show the result (last
tag, detected bump, next version) before actually creating anything.
Create the release only after the human's yes, or with the publication
green light given at launch for that version (recipe, « Publication
green light ») — never on a guess, never for an npm publication.
With an acceptance team, publish a candidate instead
(--candidate, recipe « Acceptance before publication »); the verdict
(.githooks/release-verdict.mjs (if present)) is a human gesture an agent never runs, and the
promotion (.githooks/promote-release.mjs (if present), --dry-run first) needs the same yes as
a release.
Both the promotion and a direct release also open a PR carrying the
version's acceptance note (recettes folder); if it fails, the tag and the
release stay published — report the catch-up command the script prints
(.githooks/recette-note.mjs (if present)).
04 同仓库更多 Skills
drwil-progress
Generate a static HTML dashboard (project progress, contract coverage) with nothing to deploy. Use for a quick overview before a meeting, resuming a project, or a review.
drwil-usage
Measure the tokens consumed per workstream and record the closing workstream's line in .drwil/usage.jsonl. Use when closing a workstream, or when asked what a workstream cost, to feed the dashboard and the analysis reports.
drwil-start
Start a workstream, or a queue of workstreams, with one human gesture — open a poll of the scoped briefs; the human's answer, read by the tool, moves governance to BUILD (when several briefs are chosen, the next ones are queued and started by the agent after each closing). Use when the human wants to start implementing one or several briefs.
drwil-scope
At the end of a scoping pushed (brief or intention committed on a scoping branch, its PR open), set its PR to automatic merge with the tool, without a poll — the automatic merge is the default behaviour. Use when a scoping is pushed and its PR opened, or when the human runs /drwil-scope.
run-locally
Run the project locally for development — prerequisites, success signals, known pitfalls on first startup.
refactor-without-breaking
Split or restructure existing code without changing its behavior — characterization tests first, small committed steps, bugs found committed separately. Use for every refactor.