first-five
First Five
Arguments
Raw arguments: $ARGUMENTS
Parse the arguments as the base branch to diff against. If empty, default to main.
Goal
Scan the changed files between the base branch and HEAD against the First Five checklist and report only the things worth investigating. This is a short, scannable triage list — not a full review and not a dump of every line.
The five checks:
- Error Handling — empty catches, missing error paths around fallible calls, swallowed exceptions, silent failures.
- Input Boundaries — missing length/type/format validation on user input, request fields used without validation, unbounded inputs hitting the database or external systems.
- External Calls — calls to methods/facades/APIs that may not exist or may not behave as assumed (wrong signature, wrong namespace, missing trait/macro).
- State Mutations — destructive or surprising writes (deletes, overwrites, cascades) that other code relies on.
- Assumed Dependencies — imports, classes, files, routes, views, or config keys that the code references but that may not exist.
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.
53checklist
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.
20triage
Triage a branch or diff by grouping changed files into feature areas, assigning each a risk tier (High/Medium/Low), and producing a scannable summary that helps decide where to spend review time. Use when the user asks to "triage" a branch, PR, or diff.
14