本文へ移動
cccskills
無料GitHub で公開

release

Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu
連携ツールGitHub
インストール方法を見る

含まれるファイル（1）

  • SKILL.md2.8 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Release

A kolu release is a tag on master (kolu ships only as a Nix flake; master stays the channel). Version's single source of truth: packages/server/package.json. Do these in order — nothing is committed, tagged, or pushed before the human approves.

  1. Settle inputs — version from the argument, else ask (valid semver X.Y.Z, differs from the last tag; show the feat/fix history since the last tag to inform the call — it's an editorial choice, kolu is an app, not a library). Date: default today, confirm.
  2. Preflight (refuse if any fails) — on master, clean tree, synced with origin/master, latest /ci green on HEAD.
  3. Fix the changelog — its own approved commit — audit every entry in unreleased.mdx against AGENTS.md and fix violations in place, uncommitted. Show the human the diff and AskUserQuestion to approve; iterate until approved, then commit (changelog: reconcile for ${version}). A separate commit is the point: promotion renames the file, so folding fixes into it would bury the one diff the human can actually review.
  4. Stage the promotion — uncommitted — promote the fixed unreleased.mdx body to website/src/content/changelog/<X-Y-Z>.mdx with { version, date } frontmatter — consolidate duplicate product-area ### headings (first-seen order, merge their bullets — never regroup by kind), and open with one editorial summary paragraph (the summary frontmatter field; the build fails without it). Reset unreleased.mdx to an empty open section. Set the version in packages/server/package.json.
  5. Approval gate — show the human the staged (uncommitted) diff — the promoted changelog as it will actually publish, the version bump, and the tag v${version} — and AskUserQuestion to proceed. Iterate until approved; No discards the staged changes, leaving only the approved changelog commit.
  6. Commit + push — commit (release ${version}) and push master (both commits). Do not tag yet.
  7. /ci gate — run /ci on the exact release commit. On failure, open a PR with the fix, let the human merge it, run /ci on the resulting commit, and tag that instead; never tag a commit /ci hasn't passed.
  8. Tag & publish — annotated tag v${version} on the green release commit; push it; gh release create v${version} with notes pointing at kolu.dev/changelog#v<X-Y-Z>.
  9. Verify & report — tag on master, GitHub release live, kolu.dev/changelog shows the release. Report the tag URL, the release URL, and the pin: nix run github:juspay/kolu/v${version}.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

blog-post

無料

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

ci

無料

Run this repo's CI end-to-end — kolu's policy on top of the odu runner: banned opt-out flags, x86_64-linux pinning, pool upkeep, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

dev-server

無料

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

diataxis

無料

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: the Kolu overlay below). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

dock-state

無料

The Dock's agent-state folds — one fenced source of truth in @kolu/terminal-vocab, the load-bearing order≠colour split, and the one "is something happening" question. Use when editing agentProjection or the canvas dock.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

e2e-testing

無料

E2E test conventions — semantic selectors, arrange-steps that prove the process started, runtime markers that cannot match the shell echo, and absolute-path tool invocations. Use when writing or changing a .feature scenario under packages/tests.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

juspay のスキルをすべて見る

このスキルの問題を報告する