القائمة
Refresh the managed Spec Kit section in coding agent context file(s)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | speckit-agent-context-update |
| description | Refresh the managed Spec Kit section in coding agent context file(s) |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"agent-context:commands/speckit.agent-context.update.md"} |
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.
Audits documentation completeness for a feature branch, subject, or set of existing docs — maps changes across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
General code quality review — project guideline compliance, bug detection, code quality analysis.
Code comment accuracy verification, documentation completeness assessment, comment rot detection.
Error handling review — silent failure detection, catch block analysis, error logging.
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.