メニュー
Safe conventional-commit workflow for an agent asked to commit changes. Run tests before staging, stage deliberately, write a Conventional Commits-style subject + body, never amend or force-push without explicit user approval.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git-commit-flow |
| description | Safe conventional-commit workflow for an agent asked to commit changes. Run tests before staging, stage deliberately, write a Conventional Commits-style subject + body, never amend or force-push without explicit user approval. |
| license | KohakuTerrarium License 1.0 |
| paths | ["*.py","*.ts","*.tsx","*.js","*.jsx","*.go","*.rs"] |
Use this skill any time the user asks for a commit ("commit", "check
this in", "push a patch"). The goal is a reviewable atomic commit with
a message that matches the repository's conventions — not a best-effort
git commit -am "wip".
git status + git diff to confirm you know exactly what will
be staged. Never run git add -A blind.package.json,
pyproject.toml, Makefile, or ask if unsure). Block on failures
unless the user explicitly says "commit anyway"..env files, or binary blobs, stop
and flag it to the user before staging.git add <paths> — stage files individually or by glob. Avoid
-A / . so unrelated dirty files don't hitch-hike into the
commit.git status to confirm only intended files are staged.<type>(<scope>)?: <subject> where type ∈ {feat, fix, refactor, test, docs, chore, perf, build, ci}. Keep the
subject under 72 chars.Co-Authored-By: KohakuTerrarium <noreply@kohaku-lab.org> at the end of commit message.git reset --hard, git push --force, or pass
--no-verify/--no-gpg-sign without explicit user approval.Create a custom KohakuTerrarium creature folder, then spawn and connect it into the current terrarium graph with group tools. Use when asked to make a new agent/creature/worker/specialist and wire it into a team.
Merge, split, or reorder PDF files. Use when the user mentions combining PDFs, extracting pages, or any "glue these PDFs together" request. Activates automatically in directories containing .pdf files.
Maintain a simple todo.md / plan.md workspace for multi-step tasks. Use when the user says "make a plan", "track this as a task list", or whenever a non-trivial multi-step task would benefit from being checkpointed to disk between agent turns.