본문으로 건너뛰기
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.9 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 .apm/instructions/changelog.instructions.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}.

ARGUMENTS: $ARGUMENTS

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 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월 19일 업데이트

ci

무료

Run this repo's CI end-to-end — the kolu-specific procedure on top of the odu runner: the odu MCP front door, banned opt-out flags, linux-only platform pinning, venue-pool leasing, 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월 19일 업데이트

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월 19일 업데이트

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: `.apm/instructions/diataxis.instructions.md`). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

juspay/kolu822026년 10월 19일 업데이트

evidence

무료

Produce visual PR evidence — a screenshot or video — whenever a change has on-screen impact. Tests are never a substitute; a change can be backend by cause and visible by effect. Capture via the project's e2e harness on a pu box, or by driving a live kolu with the chrome-devtools MCP; host on a GitHub release and post a `## Evidence` comment. Triggers on "post evidence", "screenshot the change", "record a video of this", "show it working", "prove it", or finishing any change whose effect is visible on screen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

juspay/kolu822026년 10월 19일 업데이트

frontend-design

무료

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

juspay/kolu822026년 10월 19일 업데이트

juspay의 스킬 모두 보기

이 스킬의 문제 신고