completeness-review

Scan codebases for stubs, TODOs, and unfinished implementations against features.md and project-plan.md.

1|1|Updated Mar 9, 2026

Search Tags:#quality assurance #code review #deployment readiness #TODOs #completeness check #stub detection

Ready to run

npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill completeness-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: completeness-review
Source: https://github.com/trevorbyrum/claude-skills-suite/tree/main/skills/completeness-review
Command: npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill completeness-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unfinished code, stubs, and TODOs from slipping into production, ensuring that features marked as complete are genuinely implemented.

Core Features & Use Cases

Pattern Scanning: Detects common markers of incomplete code like TODOs, FIXMEs, placeholders, and debug statements.
Feature Verification: Cross-references implemented code against feature definitions in features.md to ensure full functionality.
Deliverable Check: Validates that all items in the project-plan.md have corresponding, complete code implementations.
Use Case: Before deploying a new feature developed by an AI, run this skill to catch any "TODO: Implement this later" comments or functions that only return dummy data, ensuring a robust release.

Quick Start

Scan the codebase for any incomplete implementations or placeholders.

Frequently Asked Questions about completeness-review

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

FAQPage Schema

How do I scan my codebase for stubs and TODOs before deployment?▼

To scan your codebase for stubs and TODOs before deployment, run a completeness check to detect empty bodies, placeholders, and unfinished implementations, then review the generated severity report to resolve critical issues. It cross-references implemented code against feature definitions to ensure full functionality.

What is a completeness check in code review?▼

A completeness check in code review is an automated scan that identifies markers of incomplete code like TODOs, FIXMEs, placeholders, and debug statements. It validates that features marked as complete are genuinely implemented by verifying feature definitions and project deliverables against the actual codebase.

How do I verify feature completeness against a features.md file?▼

You verify feature completeness against a features.md file by scanning the codebase to cross-reference implemented code with the defined feature specifications. This process identifies and reports any critical, high, medium, or low severity incompletions where functionality is missing or only stubbed out.

Can I detect empty function bodies and placeholder code automatically?▼

Yes, you can detect empty function bodies and placeholder code automatically through pattern scanning. The scan targets common markers of incomplete code, catching functions that only return dummy data or contain unfinished implementations before they slip into production.

How do I validate project deliverables against a project-plan.md file?▼

You validate project deliverables against a project-plan.md file by running an automated check that ensures all planned items have corresponding, complete code implementations. It flags any deliverables lacking functional code, preventing unfinished features from reaching deployment.

What severity levels are reported when finding unfinished code implementations?▼

When finding unfinished code implementations, the completeness review reports incompletions across four severity levels: critical, high, medium, and low. This categorization helps prioritize which stubs, TODOs, or missing feature implementations must be resolved before a robust release.