fix-findings
Fix Review Session Findings
Read findings from the active review session and apply fixes to the codebase, then update the resolution log.
Step 1: Resolve the active session
Look for the current session:
- Check
.chalk/reviews/.current-session - If not found, check for the most recent session directory under
.chalk/reviews/sessions/ - If nothing found, stop and tell the user to run
/create-reviewfirst to start a session
Store the session ID as {session}.
Step 2: Determine which findings to load
Based on $ARGUMENTS:
- If a reviewer name is provided (e.g.
codex,gemini,gpt4,claude), sanitize it to kebab-case and load only.chalk/reviews/sessions/{session}/{reviewer}.findings.md
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-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.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13product-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