Generate Context
Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Use this skill to maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.
Optional input: a package, app, feature, context group, or architectural area to refresh first.
Workflow
- Read
references/generate-context.md for the full context contract.
- Determine mode:
- Full scan when
process/context/all-context.md is missing.
- Delta update when it exists.
- Read
process/context/all-context.md when present to identify relevant grouped context files.
- Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant
process/context/**/*.md docs.
- Produce
process/context/all-context.md PLUS process/context/{group}/all-{group}.md for each detected or approved group (see Invocation Modes below).
- Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
- Validate the generated context:
node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs
- If routing or grouped context changed, also run:
node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs
Rules
- Treat
process/context/ as durable cross-agent knowledge.
- Treat
process/context/all-context.md as the durable routing protocol; do not replace it with generated prose.
- Do not store agent-specific mechanics here unless they affect project workflow.
- Do not rewrite grouped context docs; if they are stale or mis-grouped, flag
audit-context.
- Prefer concise, factual, path-specific documentation.
- Use
pnpm terminology for package management.
- Treat validation failures as blockers before presenting context as refreshed.
Invocation Modes
| Mode |
Trigger |
Group-detection |
Output |
setup-delegation |
Called by vc-setup passing an approved-groups list |
Skip re-detection; use the list provided |
all-context.md + all-{group}.md for each approved group |
standalone-full |
Direct invocation with no groups list |
Self-detect groups via the detection table in references/generate-context.md |
all-context.md + all-{group}.md for all detected groups |
delta |
Invoked when context already exists; update context |
Self-detect; create MISSING groups only; warn on unrecognized; never delete |
all-context.md updated + any new all-{group}.md files created |
See references/generate-context.md for per-mode instructions, the Context Group Detection Table, and delta-mode group-creation rules.
1---2name: vc-generate-context3description: Generate or update the project's authoritative repository context at process/context/all-context.md. Use when repo context is missing, stale, or contradicted by code.4---56# Generate Context78> **Output style:** Follow `process/development-protocols/communication-standards.md` — answer-first, plain language, no unexplained jargon, TL;DR on long responses.910Use this skill to maintain `process/context/all-context.md`, the broad portable project knowledge layer shared by Codex and Claude. Use `process/context/all-context.md` as the context router before reading grouped docs.1112Optional input: a package, app, feature, context group, or architectural area to refresh first.1314## Workflow15161. Read `references/generate-context.md` for the full context contract.172. Determine mode:18 - Full scan when `process/context/all-context.md` is missing.19 - Delta update when it exists.203. Read `process/context/all-context.md` when present to identify relevant grouped context files.214. Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant `process/context/**/*.md` docs.225. Produce `process/context/all-context.md` PLUS `process/context/{group}/all-{group}.md` for each detected or approved group (see Invocation Modes below).236. Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.247. Validate the generated context:25 ```bash26 node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs27 ```288. If routing or grouped context changed, also run:29 ```bash30 node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs31 ```3233## Rules3435- Treat `process/context/` as durable cross-agent knowledge.36- Treat `process/context/all-context.md` as the durable routing protocol; do not replace it with generated prose.37- Do not store agent-specific mechanics here unless they affect project workflow.38- Do not rewrite grouped context docs; if they are stale or mis-grouped, flag `audit-context`.39- Prefer concise, factual, path-specific documentation.40- Use `pnpm` terminology for package management.41- Treat validation failures as blockers before presenting context as refreshed.4243## Invocation Modes4445| Mode | Trigger | Group-detection | Output |46|---|---|---|---|47| `setup-delegation` | Called by vc-setup passing an approved-groups list | Skip re-detection; use the list provided | `all-context.md` + `all-{group}.md` for each approved group |48| `standalone-full` | Direct invocation with no groups list | Self-detect groups via the detection table in `references/generate-context.md` | `all-context.md` + `all-{group}.md` for all detected groups |49| `delta` | Invoked when context already exists; update context | Self-detect; create MISSING groups only; warn on unrecognized; never delete | `all-context.md` updated + any new `all-{group}.md` files created |5051See `references/generate-context.md` for per-mode instructions, the Context Group Detection Table, and delta-mode group-creation rules.
withkynam