Mission

You are the fixer. You must read .documents/review/AI_REVIEW.md, implement fixes, and write a fix log to .documents/review/AI_CHANGES.md.

Allowed writes

• •Source code files as needed to implement fixes.
• •.documents/review/AI_CHANGES.md (create if missing).
• •Optional: You MAY update status in .documents/review/AI_REVIEW.md only for the matching item by setting Status: Done|Blocked (no rewriting reviewer text).

Workflow

1. •Parse the latest round in .documents/review/AI_REVIEW.md.
2. •Select a batch to fix (Blocker first, then High). Keep batch size small (e.g., 3-5 items) unless user requests otherwise.
3. •Make minimal, targeted changes. Avoid feature additions and broad refactors.
4. •Ensure acceptance criteria per item are met (run tests/linters if available and safe).
5. •Append to .documents/review/AI_CHANGES.md:
   • •Round, date
   • •For each fixed item: ID, summary, files changed, commands run (if any), outcome
   • •Any remaining known issues / follow-ups

Logging format (.documents/review/AI_CHANGES.md)

• •# AI Changes
• •## Round X (YYYY-MM-DD)
• •- [R{X}-NN] ...

Rules

• •If a fix requires a design decision, write the smallest safe fix and note alternatives.
• •If you can’t safely fix, explain why and propose next steps in .documents/review/AI_CHANGES.md.

Resources

• •

  Use scripts/scaffold_doc.py to create the target doc skeleton:

• •

  Use --template assets/TEMPLATE.md to scaffold from the skill-specific template.

• •

  Use --append to add a dated subsection without overwriting.

  • •python3 scripts/scaffold_doc.py --output .documents/review/AI_CHANGES.md --title "Ai Changes" --sections "Round, Changes, Commands, Follow-ups"
• •

  Reference checklist: references/CHECKLIST.md

• •

  Base template: assets/TEMPLATE.md

Write Guardrails

• •write target must be under .documents/