Refresh the managed Spec Kit section in coding agent context file(s)
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Refresh the managed Spec Kit section inside the active coding agent's context/instruction file (e.g. CLAUDE.md, .github/copilot-instructions.md, AGENTS.md).
The script reads the agent-context extension config at
.specify/extensions/agent-context/agent-context-config.yml to discover:
context_file — the path of the coding agent context file to manage.context_files — optional project-relative paths for multiple coding agent context files. When non-empty, the script updates each listed file and the list takes precedence over context_file.context_markers.start / .end — the delimiters surrounding the managed section. Defaults to <!-- SPECKIT START --> and <!-- SPECKIT END --> when the field is missing.It then creates, replaces, or appends the managed block so that the section points at the most recent plan path when one can be discovered (specs/<feature>/plan.md).
If context_files and context_file are empty, the command reports nothing to do and exits successfully. Context file paths must stay project-relative; absolute paths, Windows drive paths, backslash separators, and .. path segments are rejected.
.specify/extensions/agent-context/scripts/bash/update-agent-context.sh [plan_path].specify/extensions/agent-context/scripts/powershell/update-agent-context.ps1 [plan_path]When plan_path is omitted, the script auto-detects the most recently modified specs/*/plan.md.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。