メニュー
This skill should be used when drafting a git commit message from staged or proposed changes. Produces a user-impact subject and a concise body. Deliberately avoids motivation paragraphs (those belong in the PR description, not the commit log).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Multi-agent design argument — Azusa challenges Mugi's plan, Mugi revises. Used by /kon:design after exploration and initial plan draft.
Multi-agent software engineering workflow. Use this skill whenever the user types a /kon: command — including /kon:team, /kon:design, /kon:quick, /kon:debug, /kon:ask, /kon:review, /kon:review-pr, /kon:hunt, /kon:gc, /kon:research, /kon:describe-issue, /kon:begin, /kon:finish, /kon:summarize, /kon:retro, /kon:address-comments, /kon:todo, /kon:understand-codebase. Orchestrates specialized agents: Azusa (explorer), Jun (researcher), Mugi (planner), Yui (implementer), Mio (reviewer), Sawako (cleaner), Nodoka (summarizer).
This skill should be used by all kon agents at startup, before beginning work, to load relevant memory from public and repo indexes with relevance-based ordering and a 10-entry cap. Consumers: Azusa, Mugi, Mio, Jun, and any future memory-reading agent.
Convention for per-repo skill directories at ~/.kon/projects/<repo-name>/skills/<name>/SKILL.md. Each named subdirectory is one skill. Agents load all SKILL.md files as the first step before memory entries.
When requirements, code behavior, root cause, or review scope is unclear — ask the user before proceeding. Never invent facts, assumptions, or fixes. Applies to every kon stage and every agent.
Route plain-text user messages while a /kon:begin session is open. Reuse the same session JSON — never init a second session for sub-turns.
| name | commit-message |
| description | This skill should be used when drafting a git commit message from staged or proposed changes. Produces a user-impact subject and a concise body. Deliberately avoids motivation paragraphs (those belong in the PR description, not the commit log). |
Consumers: any task that drafts a commit message after a successful run.
Core principles (always): follow skills/core-principles — subject states user impact concisely; no motivation paragraphs or padding.
type(scope): subject), keep that format; otherwise freeform
pyproject.toml has [tool.commitizen], or .cz.toml / commitlint.config.js exists| Bad | Good |
|---|---|
update auth.py and tests | Reject empty emails before hashing |
fix bug | Stop retry storm on 5xx from upstream |
address review comments | Enforce non-empty email at signup |
The body is for the future bisecting engineer, not the current reviewer:
<subject — one line, ≤70 chars, user-impact>
<body — ≤3 sentences; omit entirely if nothing durable to add>
Provide raw text to the caller — do not wrap in a code fence by default (breaks piping to git commit -F -).
When presenting to the user as a readable deliverable, wrap in a single fenced code block.
git commit — everAgents never run git commit or git push. The skill produces text only.
Present the draft in a fenced code block so the user can copy it and run:
git commit -m "$(cat <<'EOF'
<paste subject here>
<paste body here>
EOF
)"
The user decides when and whether to commit.
Co-Authored-By trailerkon-drafted commits do not include co-author attribution lines.