What problem does it solve?
Eliminates manual commit message writing and the tedious, error-prone step of updating project documentation before committing and pushing code changes, ensuring commits follow Conventional Commits and docs stay in sync with staged diffs.
Core Features & Use Cases
- Conventional Commit Generation: Produce a single Conventional Commits-style message (in Japanese) from the staged changes, selecting appropriate type and optional scope.
- Built-in Doc Update Flow: Read and execute the doc-updater procedure from references to decide and apply documentation edits based solely on git diff --cached, then re-stage any updated docs.
- Safe Git Operations: Validate staging state, avoid destructive operations, commit with SKIP_DOC_UPDATER=1 to prevent recursion, and push the current branch; useful for agents or developers who want automated, auditable commits that include documentation updates.
Quick Start
Ask the agent to generate a Japanese Conventional Commit message from the current staged changes, run the embedded doc-updater process if needed, stage any doc edits, commit with SKIP_DOC_UPDATER=1, and push the current branch.