vc:docs
The vc:docs skill analyzes codebases and manages project documentation through three operations: init creates initial documentation from codebase analysis, update refreshes existing docs based on code changes, and summarize provides quick codebase overviews. Use this skill when you need to generate, maintain, or review project documentation in the vibecode-pro-max-kit repository, where documentation context is stored in the process/context directory.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-docs && cp -r /tmp/vc-docs/.claude/skills/vc-docs ~/.claude/skills/vc-docsSKILL.md
# Documentation Management Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation. ## Default (No Arguments) If invoked without arguments, use `AskUserQuestion` to present available documentation operations: | Operation | Description | |-----------|-------------| | `init` | Analyze codebase & create initial docs | | `update` | Analyze changes & update docs | | `summarize` | Quick codebase summary | Present as options via `AskUserQuestion` with header "Documentation Operation", question "What would you like to do?". ## Subcommands | Subcommand | Reference | Purpose | |------------|-----------|---------| | `/vc:docs init` | `references/init-workflow.md` | Analyze codebase and create initial documentation | | `/vc:docs update` | `references/update-workflow.md` | Analyze codebase and update existing documentation | | `/vc:docs summarize` | `references/summarize-workflow.md` | Quick analysis and update of codebase summary | ## Routing Parse `$ARGUMENTS` first word: - `init` → Load `references/init-workflow.md` - `update` → Load `references/update-workflow.md` - `summarize` → Load `references/summarize-workflow.md` - empty/unclear → AskUserQuestion (do not auto-run `init`) ## Shared Context For this repo, durable agent-facing documentation lives in `process/context/`, not `./docs`. Read `process/context/all-context.md` first to choose the relevant root file or context group. Use `audit-context` after adding, moving, splitting, or grouping context files. **IMPORTANT**: **Do not** start implementing code.
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.