review-changes
Review Changes
Orchestrate the full review pipeline: handoff → review → fix. This skill chains three phases with user checkpoints between each.
Phase 1: Create Handoff
Run the full handoff generation inline (do not invoke /create-handoff as a sub-skill — execute the steps directly):
Step 1.1: Determine the session name
- If the user provided
$ARGUMENTS, sanitize it using a shell command — not LLM interpretation — to produce a safe kebab-case string:
Use the output as the session name. If the sanitized result is empty, fall back to option 2.echo "$ARGUMENTS" | tr '[:upper:]' '[:lower:]' | sed -E 's/[^a-z0-9-]+/-/g; s/^-+//; s/-+$//; s/-{2,}/-/g' - Otherwise, infer from the current branch name (e.g.
feature/issue-24-authentication→issue-24-authentication) - If on
main/master, ask the user what to name the session
Step 1.2: Create the session directory
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
24create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15product-context-docs
Create and update in-repo product context documentation in /docs (product profile, features, sitemap, architecture, tech stack). Use when asked to document a product, bootstrap /docs structure, or refresh product/tech context docs for a repo.
11