post-implementation-review

Reviews completed implementations through three agent passes to produce concrete proposed fixes.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/tschallacka/ai-skills --skill post-implementation-review-tschallacka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-implementation-review
Source: https://github.com/tschallacka/ai-skills/tree/main/post-implementation-review
Command: npx skills add https://github.com/tschallacka/ai-skills --skill post-implementation-review-tschallacka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code is written, residual bugs, undecided choices, and unverified paths often remain hidden. This Skill runs a structured after-the-fact review that finds what an implementation left behind and ends with concrete, minimal proposed fixes instead of vague impressions. ## Core Features & Use Cases - Three-pass review: implementer self-analysis grounded in file:line evidence, an independent solutions agent that verifies findings and proposes minimal fixes, and a critical-feedback agent that stress-tests each fix for over-reach, under-reach, and regressions. - Classified findings: every suspected issue is labeled CONFIRMED, PARTIAL, or NOT-A-BUG with a reproducible trigger, and each fix gets an apply / apply-with-changes / reject / document-only verdict. - Durable report: results are written to .plans/<initiative>/post-implementation-review.md alongside the brainstorm and plan, so declined fixes stay recorded and nothing is silently lost. - Use Case: You just finished a shell-script change touching process-control code and only verified one path. Run this review to have three independent passes confirm or dismiss your suspicions and deliver exact replacement code for each real defect. ## Quick Start Review what we just built and propose fixes for anything the implementation left behind.

Frequently Asked Questions about post-implementation-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code after implementing a feature?▼

Run a post-implementation review that re-reads the changed files with fresh eyes, classifies each suspected issue as confirmed, partial, or not-a-bug with file:line evidence, then has independent agents verify findings and propose minimal fixes.

When should I run a post-implementation review?▼

Run it when an implementation ends with known potential bugs, undecided choices, or partially verified behavior, especially in shared or process-control code. Skip it for trivial, fully verified changes with no residual unknowns.

How is post-implementation review different from pre-implementation planning review?▼

Post-implementation review examines code that already exists to find defects it left behind, while pre-implementation adversarial review happens during planning before any code is written. They are complementary bookends around the implementation step.

What happens to fixes that are declined during code review?▼

Declined fixes are recorded in the review report's Decision section with the reason for rejection, so they remain visible and are not silently lost. The report is stored at .plans/<initiative>/post-implementation-review.md.

Why use multiple independent agents for code review?▼

Independent agents with fresh context catch blind spots the original implementer has. The solutions agent verifies findings without taking them on faith, and the critical-feedback agent detects over-reaching or under-reaching fixes the first two passes missed.