triage
Triage
Arguments
Raw arguments: $ARGUMENTS
Parse the arguments as the base branch to diff against. If empty, default to main.
Goal
Produce a risk-ordered map of the changes between the base branch and HEAD, grouped by feature area, so the user can decide where to spend their review time. The output is a triage report — not a review.
Do not perform the review. Do not make suggestions. Do not propose fixes. Do not flag specific lines to verify. The user reads this map and decides for themselves what to dig into.
Instructions
1. Get the diff
Run git diff --name-status <base>...HEAD for a file-level overview, then git diff <base>...HEAD to see the actual changes. If there are no changes, tell the user and stop.
More from unlearndev/skills
spec-generator
Generate a detailed product specification document from a vague idea, rough description, or supporting materials (UI sketches, screenshots, notes, existing docs). Use this skill whenever the user wants to turn a rough concept into a structured spec — even if they say things like "write up a spec for...", "turn this idea into a requirements doc", "I have this rough idea for a product", "help me spec this out", "create a PRD for...", or uploads images/files and wants a spec written from them. Covers all product types including internal tools. Trigger this skill even if the request seems simple — a vague one-liner idea deserves a proper spec just as much as a detailed brief.
56code-review
Code review staged changes or a specific area of the codebase, optionally delegating to a chosen agent. Use when the user wants a code review.
54checklist
Convert the current plan, code review, or structured content in context into a persistent markdown checklist file under .claude/plans/
52feature-generator
Generate a detailed features.md document from a spec.md, or sync changes between spec.md and features.md when either file is updated. Use this skill whenever the user wants to expand a product spec into a full feature list, asks to "generate features", "create features.md", "expand the spec", "update features from spec", or "sync spec and features". Also trigger when the user has modified either spec.md or features.md and wants to keep them in sync. Always use this skill when both files are in play together.
51review-order
Prepare a structured, scannable review checklist for a branch or diff, grouped by feature change and applying the four-pass review order (Types, Data Flow, Business Logic, Edge Cases) within each feature. Use when the user asks to "prep a review", "review order", or wants a checklist to manually walk through changes.
20first-five
Scan a branch or diff against the First Five checklist (Error Handling, Input Boundaries, External Calls, State Mutations, Assumed Dependencies) and report only genuine concerns. Use when the user asks to "run the first five" on a branch or diff.
19