speckit-agent-context-update
$
npx mdskill add foxminchan/BookWorm/speckit-agent-context-updateUpdates the coding agent context file with the latest Spec Kit plan
- Synchronizes agent context with the most recent feature plan
- Requires spec-kit structure with .specify/ directory and agent context file
- Uses configuration from agent-context-config.yml to locate and update context
- Inserts or replaces content within specified start and end markers in the context file
SKILL.md
.github/skills/speckit-agent-context-updateView on GitHub ↗
--- name: speckit-agent-context-update description: Refresh the managed Spec Kit section in the coding agent context file compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: agent-context:commands/speckit.agent-context.update.md --- # Update Coding Agent Context 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`). ## Behavior 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_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_file` is empty or the file cannot be located, the command reports nothing to do and exits successfully. ## Execution - **Bash**: `.specify/extensions/agent-context/scripts/bash/update-agent-context.sh [plan_path]` - **PowerShell**: `.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`.
More from foxminchan/BookWorm
- aspire>-
- aspire-deployment**WORKFLOW SKILL** — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, or AWS. WHEN: "deploy Aspire app", "publish Aspire artifacts", "deploy to Azure Container Apps", "generate Kubernetes artifacts", "tear down Aspire deployment". INVOKES: aspire CLI, Aspire docs, target cloud/container CLIs. FOR SINGLE OPERATIONS: use generic Azure, Kubernetes, Docker, or AWS tools only when no Aspire AppHost exists.
- aspire-init>-
- aspire-monitoring>-
- aspire-orchestration>-
- aspireify>-
- book-catalogSearch and recommend books from BookWorm's catalog. Use when customers ask about finding books, getting personalized recommendations, exploring genres, discovering authors, or comparing titles.
- catalog-documentation-creatorGenerates EventCatalog documentation files (services, agents, events, commands, queries, domains, flows, channels, containers) with correct frontmatter, folder structure, and best practices. Use when user asks to "document a service", "document an agent", "document an AI agent", "create EventCatalog files", "add an event to the catalog", "document my architecture", "generate catalog documentation", "create documentation for my microservice", or "document a database".
- code-to-catalogTurns a codebase into EventCatalog documentation through an evidence-based interview. Scans the code first, proposes an architectural model (domains, services, agents, messages, channels), grills the user on the structural decisions, produces a reviewable plan file, then hands off to catalog-documentation-creator. Use when user says "document my codebase in EventCatalog", "turn this repo into a catalog", "model my code as a catalog", "document my agents", "document my AI agents", "grill me on my architecture", "update my catalog from the code", "reconcile my catalog with my code", or "I don't know where to start documenting this codebase". Works for brand-new catalogs AND for updating existing catalogs that have drifted from the code.
- csharp-tunitGet best practices for TUnit unit testing, including data-driven tests