gideas

Run markdown linting from tools/spec-lint/, fix issues, and rerun until clean

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: writes a ranked checklist to plans/AUDIT.md of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", or calls ponytail-audit. One-shot report, does not apply fixes.

Fix ponytail audit items from plans/AUDIT.md one at a time. For each item: implementer fix → ponytail-review → normal review → quality gate → mark done → commit. Cycle until reviewer is happy at each stage. Complements ponytail-audit.

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or calls ponytail-review. Complements the correctness-focused reviewer subagent — this one only hunts complexity.

Use when executing a project folder under plans/ that contains SPEC.md, PLAN.md, and PHASE_XX.md files.

Fix the first incomplete checklist item in plans/<project>/REVIEW.md, commit the fix, then stop. Does not commit REVIEW.md — it is gitignored by design.

Review the current repository state against a project's SPEC.md in plans/<project-name>/ and produce a checklist of issues in REVIEW.md. Use when you need a methodical spec-compliance audit of the present codebase.

Use when a project folder under plans/ contains SPEC.md and needs PLAN.md plus PHASE_XX.md files.

Use when turning a project idea or feature request into an implementation-ready SPEC.md under plans/.

Use when creating and publishing a new GitHub release with an auto-generated changelog and README review.

Fix every item in an existing REVIEW.md through strict fix → reviewer cycles. Use when you have a review checklist and need every issue addressed with no shortcuts.

Commit and push all the changes (update git ignore where needed)

Deep-review the spec — starts a fresh review of all spec documents against AGENTS.md (producing REVIEW.md), or continues an existing review by walking through unresolved issues with the user