vc:watzup
The vc:watzup skill generates a read-only handoff summary of the current Git repository state, including branch status, worktrees, local and remote references, active project plans, and suggested next steps. Use it when resuming work or handing off context to understand what has been done and what might be next, without executing any changes or making authoritative plan decisions.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-watzup && cp -r /tmp/vc-watzup/.claude/skills/vc-watzup ~/.claude/skills/vc-watzupSKILL.md
# Watzup Summarize the current repo state for handoff and resume work. This is a helper skill only. - Do use it for read-only branch, worktree, and active-plan summaries. - Do use it to surface likely selected-plan context when it can be proven or safely hinted. - Do not use it to choose a plan authoritatively. - Do not use it to approve execution, resume execution, or mutate repo/process state. ## Core Contract `watzup` is advisory. - Evidence comes from git, worktree metadata, and `process/*` plan inventory. - Selected-plan awareness is a hint, not a command. - Next-step recommendations are suggestions, not workflow gates. If a user needs execution, the repo still requires explicit plan selection and `ENTER EXECUTE MODE`. ## Invocation Run the local scanner: ```bash node .claude/skills/watzup/scripts/watzup-scan.cjs --json ``` Useful flags: ```bash node .claude/skills/watzup/scripts/watzup-scan.cjs node .claude/skills/watzup/scripts/watzup-scan.cjs --json --max-branches 8 --plan-limit 6 node .claude/skills/watzup/scripts/watzup-scan.cjs --selected-plan process/general-plans/active/example_PLAN_27-05-26.md node .claude/skills/watzup/scripts/watzup-scan.cjs --since "14 days ago" node .claude/skills/watzup/scripts/watzup-scan.cjs --fetch ``` ## Input Sources The scanner reads from: - `git status --short --branch` - `git worktree list --porcelain` - local and remote branch refs plus sampled recent commits - `process/general-plans/active/` - `process/features/*/active/` - optional session-state hints if a local session id is present It does not scan upstream `plans/**`, and it never treats a selected-plan hint as execute authority. ## Output Shape The default output is a human-readable report with these sections: - Current State - Recent Work - In-Flight Plans - Next Steps - Warnings `--json` returns the same information as structured data. If the scanner fails, say that explicitly and fall back to the minimal read-only commands: ```bash git status --short --branch git worktree list --porcelain git for-each-ref --format='%(refname:short) %(committerdate:iso8601) %(objectname:short) %(subject)' refs/heads refs/remotes find process/general-plans/active process/features -path '*/active/*' -type f | sort ``` ## Safety Rules 1. Read-only only. No branch switching, plan edits, or fetch unless `--fetch` is explicit. 2. Treat selected-plan inference as tentative unless it came from an explicit `--selected-plan` argument. 3. Remote branch data is stale-by-default unless `--fetch` is explicit. 4. Use this for session handoff and quick repo orientation, not for workflow control. 5. If the scan cannot prove something, emit a warning instead of guessing. Good trigger phrases: - `what's in flight` - `give me a handoff summary` - `what active plans do we have` - `show branch and worktree status` - `what should I look at next` Load `references/watzup-workflow.md` when you need the project's decision tree or hint-priority rules.
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.