vc:generate-context
This skill maintains `process/context/all-context.md`, a centralized repository knowledge layer that documents project architecture, tooling, active plans, and grouped context files. Use it when the context file is missing, outdated, or conflicts with actual code state. It performs either a full scan or delta update depending on whether the file exists, validates the output against a schema, and flags stale grouped context docs for separate auditing.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-generate-context && cp -r /tmp/vc-generate-context/.claude/skills/vc-generate-context ~/.claude/skills/vc-generate-contextSKILL.md
# Generate Context 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 1. Read `references/generate-context.md` for the full context contract. 2. Determine mode: - Full scan when `process/context/all-context.md` is missing. - Delta update when it exists. 3. Read `process/context/all-context.md` when present to identify relevant grouped context files. 4. Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant `process/context/**/*.md` docs. 5. Produce exactly one updated file: `process/context/all-context.md`. 6. Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references. 7. Validate the generated context: ```bash node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs ``` 8. If routing or grouped context changed, also run: ```bash 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.
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I''ll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I''ll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>
EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features/*/active/ only. Use after approach is decided.