Auto-commit changes after a Spec Kit command completes
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Automatically stage and commit all changes after a Spec Kit command completes.
This command is invoked as a hook after (or before) core commands. It:
after_specify hook, the event is after_specify; if before_plan, the event is before_plan).specify/extensions/git/git-config.yml for the auto_commit sectionauto_commit.default if no event-specific key existsmessage if configured, otherwise a default messagegit add . + git commitDetermine the event name from the hook that triggered this command, then run the script:
.specify/extensions/git/scripts/bash/auto-commit.sh <event_name>.specify/extensions/git/scripts/powershell/auto-commit.ps1 <event_name>Replace <event_name> with the actual hook event (e.g., after_specify, before_plan, after_implement).
In .specify/extensions/git/git-config.yml:
auto_commit:
default: false # Global toggle — set true to enable for all commands
after_specify:
enabled: true # Override per-command
message: "[Spec Kit] Add specification"
after_plan:
enabled: false
message: "[Spec Kit] Add implementation plan"
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
日本語の概要は準備中です。原文の説明を表示しています。
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。