Validate current branch follows feature branch naming conventions
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Validate that the current Git branch follows the expected feature branch naming conventions.
git rev-parse --is-inside-work-tree 2>/dev/null[specify] Warning: Git repository not detected; skipped branch validation
Get the current branch name:
git rev-parse --abbrev-ref HEAD
The branch name must match one of these patterns:
^[0-9]{3,}- (e.g., 001-feature-name, 042-fix-bug, 1000-big-feature)^[0-9]{8}-[0-9]{6}- (e.g., 20260319-143022-feature-name)If on a feature branch (matches either pattern):
✓ On feature branch: <branch-name>specs/:
specs/<prefix>-* where prefix matches the numeric portionspecs/<prefix>-* where prefix matches the YYYYMMDD-HHMMSS portion✓ Spec directory found: <path>⚠ No spec directory found for prefix <prefix>If NOT on a feature branch:
✗ Not on a feature branch. Current branch: <branch-name>Feature branches should be named like: 001-feature-name or 20260319-143022-feature-nameIf Git is not installed or the directory is not a Git repository:
SPECIFY_FEATURE environment variable as a fallbackまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。