vc-review-situation

Summarizes git branch state, worktrees, and active plans into read-only handoff reports.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-review-situation-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-review-situation
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-review-situation
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-review-situation-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When resuming work or handing off a session, developers waste time manually reconstructing repo context: which branches are active, what worktrees exist, which plans are in flight, and what to check next. This Skill automates that orientation with a single read-only scan. ## Core Features & Use Cases - Situation Scan: Runs a Node.js scanner that collects current branch, dirty state, ahead/behind counts, worktrees, ranked local/remote refs, and recent commits into a text or JSON report. - Active Plan Inventory: Discovers unfinished plans under process/general-plans/active/ and process/features/*/active/, with advisory selected-plan hints from explicit flags, session state, or a single primary plan. - Deep and Program Review Modes: Reads umbrella plans, phase reports, and handoff sections to produce full program briefings with ASCII diagrams, decision logs, and gap lists. - Use Case: At the start of a session after a long break, ask for a handoff summary to instantly see branch status, in-flight plans, warnings, and suggested next steps without touching repo state. ## Quick Start Ask the assistant to run the review-situation scan and give you a handoff summary of current branch state and active plans.

Frequently Asked Questions about vc-review-situation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a handoff summary of my git repo state?

Run the review-situation-scan.cjs script with Node.js from the repo root. It outputs Current State, Recent Work, In-Flight Plans, Next Steps, and Warnings sections, or structured data with the --json flag.

How to list active plans across git worktrees and branches?

The scanner walks process/general-plans/active/ and process/features/*/active/ in every worktree, plus tracked plan files on ranked local and remote refs. Plans are deduplicated by content hash and ranked by proximity to the current branch.

Does the scan modify my repository or fetch remotes automatically?

No, the scan is strictly read-only and never switches branches, edits plans, or fetches by default. Remote data stays stale unless you explicitly pass the --fetch flag, and a failed fetch produces a warning.

What happens when multiple primary plans are active?

The scanner refuses to infer a selected plan when more than one primary plan exists locally and emits a warning instead. Only an explicit --selected-plan argument, a session-state hint, or exactly one primary plan produces a hint.

Why does the scanner report stale remote branch information?

Remote refs come from local git metadata, which only updates on fetch. Without the --fetch flag the tool warns that remote branches reflect local refs only, so you should fetch before treating ahead/behind state as current.