메뉴
This skill should be used when the user asks to "generate commit message", "write a commit msg", "ai commit", "generate a conventional commit", "write my commit", or wants an LLM to draft a commit message from the staged diff.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user runs "/insights-audit", asks to "validate the insights report", "audit the report against my projects", "check what the report got wrong", or wants to cross-check an /insights-generated HTML report against actual GitHub repos and local project directories.
This skill should be used when the user asks to "end session", "capture state", "session summary", "what changed this session", "summarize repos", "write session notes", or wants to capture multi-repo state at the end of a work session.
Fill in the Patterns & Surprises section of the latest session reflect file and write the completed review to .ctx/logs/self-review/. Use when the user runs "/self-review", asks to "fill in the reflect", "write the session review", or "what patterns did we hit".
Use when working on the rslm project — Recursive Language Model inference engine in Rust. Triggers on "rslm", "RLM", "recursive language model", "rhai built-ins", "ctx_grep", "ctx_slice", "rlm_call", "rslm-core", "rslm-providers", "rslm-store", or any question about running queries, ingesting documents, or writing Rhai scripts for the RLM loop.
This skill should be used when the user asks to "review this diff", "ai review", "security review my changes", "review before push", "check my code for issues", or wants an LLM-based security and correctness review of uncommitted or unpushed changes.
Use this skill when the user says "build a harbor adapter", "adapt this benchmark for harbor", "harbor adapter for X", "port this benchmark to harbor", or wants to integrate any benchmark dataset into the Harbor evaluation framework (https://harborframework.com).
| name | commit-msg |
| description | This skill should be used when the user asks to "generate commit message", "write a commit msg", "ai commit", "generate a conventional commit", "write my commit", or wants an LLM to draft a commit message from the staged diff. |
| model | haiku |
| effort | low |
| allowed-tools | ["Bash","Read"] |
Generate a conventional commit message from the staged diff using an LLM. Present for confirmation before committing. Never commits without explicit user approval.
git diff --staged
If the staged diff is empty: inform the user nothing is staged and stop. Suggest
git add <files> first.
git log --oneline -5
Use this to match the project's existing commit message conventions (prefix style, scope usage, verbosity).
Compose a prompt:
You are an expert at writing conventional commit messages.
Based on the staged diff and recent commit history below, generate a commit message
following the Conventional Commits specification:
<type>[optional scope]: <description>
[optional body]
Rules:
- type: feat | fix | refactor | chore | docs | test | perf | ci | build
- description: lowercase, imperative mood, no period, ≤72 chars
- scope: optional, lowercase, matches the subsystem changed (e.g. handler, protocol, cli)
- body: optional, wrap at 100 chars, explain WHY not WHAT, use bullet points for multiple changes
- Do NOT add a footer unless there is a breaking change or issue reference
- Output ONLY the commit message — no preamble, no explanation
RECENT COMMITS (for style context):
<git log output>
STAGED DIFF:
<git diff --staged output>
Display the generated message clearly:
Generated commit message:
feat(handler): add streaming output for ephemeral containers
Wires ContainerOutput protocol messages through the channel-based dispatch
path so ephemeral run output streams to the CLI in real time.
Commit with this message? [y/N/edit]
Options:
y — commit immediately with the messageN (default) — abort, user will commit manuallyedit — open the message in $EDITOR for modification, then confirm againIf the user confirms, run:
git commit -m "$(cat <<'EOF'
<message>
EOF
)"
Never use --no-verify. Always let pre-commit hooks run.
If commit fails with 1Password: agent returned an error: instruct user to unlock
1Password and retry. No config change needed.
Run cargo-gate before commit-msg on Rust projects to ensure the commit is clean.
Optionally run ai-review first if the diff involves security-sensitive paths.