design-implementation-reviewer

Name: design-implementation-reviewer
Availability: InStock
Author: takusaotome

Review code implementations for correctness bugs and goal achievement.

5|4|Updated Nov 9, 2025

Search Tags:#code review #debugging #root cause analysis #end-to-end testing #requirements verification #logic errors #correctness validation

Ready to run

npx skills add https://github.com/takusaotome/claude-skills-library --skill design-implementation-reviewer-takusaotome

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-implementation-reviewer
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/design-implementation-reviewer
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill design-implementation-reviewer-takusaotome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you verify whether code actually works correctly and meets the expected results, instead of merely matching a design document.

Core Features & Use Cases

Three-layer critical review focused on code quality, end-to-end execution flow, and goal achievement.
Bug-finding with skepticism to surface defects the design may have missed, including edge cases and failure paths.
Evidence-structured findings with severity, root cause, fix recommendations, and required test plans for critical/high issues.

Quick Start

Use the design-implementation-reviewer skill to critically review the provided code for correctness, bugs, and whether it achieves the expected results with real data.

Frequently Asked Questions about design-implementation-reviewer

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

FAQPage Schema

How do I verify code correctness and find logic errors beyond matching the design document?▼

To verify code correctness and find logic errors, perform a three-layer critical review: inspect code quality, trace end-to-end execution flow, and validate goal achievement. This surfaces defects like edge cases and failure paths that the original design may have missed.

What is the best way to conduct a deep code review for root cause analysis?▼

The best way to conduct a deep code review for root cause analysis is to apply bug-finding with skepticism, validating whether the implementation works with real data. Structure findings by severity, providing root cause identification and fix guidance for each detected defect.

How do I check if my code implementation actually achieves the expected end-to-end behavior?▼

To check if your code achieves expected end-to-end behavior, perform goal achievement verification alongside execution flow tracing. This validates that the implementation functions correctly with real data, rather than just superficially matching design specifications.

Does this code review approach include security vulnerability scanning?▼

No, this code review approach explicitly excludes security vulnerability scanning. It focuses entirely on correctness validation, requirements verification, and detecting logic errors to ensure the implementation achieves expected end-to-end goals.

How do I create test plans for critical bugs found during requirements verification?▼

To create test plans for critical bugs found during requirements verification, generate dedicated test cases specifically for critical and high severity issues. Structure these test plans alongside the root cause analysis and fix recommendations for each finding.