Is this different from a standard linter?

Yes. While it checks code quality, its primary focus is 'chain integrity'—ensuring that what was discussed and planned is exactly what was built.

Does this skill automatically fix my code?

No, the Technical Review skill is designed to identify problems and gaps, not solve them. It provides specific feedback for you to address manually or via other agents.

What documents does the Technical Review skill need?

It analyzes discussion, specification, and planning artifacts (usually found in your docs/workflow folder) to verify the entire implementation chain.

When is the best time to trigger a Technical Review?

It should be used as the sixth phase of the workflow, after implementation is complete but before merging or shipping the code.

Technical Review Workflow

Name: Technical Review Workflow
Author: leeovery

byleeovery

•

Productivity & Workflow

Validates implementation integrity by tracing project decisions from initial discussion through to final code delivery.

About

This skill serves as a rigorous quality gate for Claude Code, acting as an expert reviewer with a fresh perspective to ensure implementation aligns perfectly with previous research, discussions, specifications, and plans. By verifying the 'chain of integrity,' it identifies requirements that were lost in translation, tasks that were missed in the planning phase, or edge cases that were discussed but never coded. It produces structured, actionable feedback—requesting changes or providing approval—without directly modifying your codebase, ensuring human oversight remains at the center of the development lifecycle.

Key Features

Specification Coverage: Ensures all validated requirements are present in the implementation.
Structured Feedback: Produces detailed reports with clear 'Approve' or 'Request Changes' outcomes.
Chain Verification: Traces requirements from initial discussion to final code.
Plan Compliance: Verifies that all tasks and acceptance criteria were fully met.
Contextual Code Review: Evaluates quality based on specific project and framework conventions.
1 GitHub stars

Use Cases

Final quality gate check before merging a feature branch to ensure all criteria were met.
Verifying that complex architectural decisions made during planning didn't drift during the coding phase.
Ensuring edge cases identified in early research are actually covered by the final test suite.

About

Key Features

Specification Coverage: Ensures all validated requirements are present in the implementation.
Structured Feedback: Produces detailed reports with clear 'Approve' or 'Request Changes' outcomes.
Chain Verification: Traces requirements from initial discussion to final code.
Plan Compliance: Verifies that all tasks and acceptance criteria were fully met.
Contextual Code Review: Evaluates quality based on specific project and framework conventions.
1 GitHub stars

Use Cases

Final quality gate check before merging a feature branch to ensure all criteria were met.
Verifying that complex architectural decisions made during planning didn't drift during the coding phase.
Ensuring edge cases identified in early research are actually covered by the final test suite.