665,000+ skills indexed

whoabuddyCOMMUNITY

Explore all skills by this author →

Verified:Website 𝕏@whoabuddydev GitHub

check-code-complete

Scans source files for TODO, FIXME, HACK, and XXX markers with file:line references.

2|5|Updated Jan 2, 2026

Search Tags:#code-quality #todo #static-analysis #lint #code-review #dead-code

One-click install

npx skills add https://github.com/whoabuddy/claude-knowledge --skill check-code-complete

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: check-code-complete
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/check-code-complete
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill check-code-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineering teams prevent merged code from containing unfinished work by scanning for common indicators like TODOs, stubs, dead code, and stray debug artifacts.

Core Features & Use Cases

Detects TODO:, FIXME:, HACK:, and XXX: markers in source files.
Flags empty functions, incomplete implementations, and unused or legacy code blocks.
Produces a concise report with file:line references to speed up remediation during code review.

Quick Start

Run the check-code-complete command in the repository root or point it at a specific path to scan and surface issues before merging.

Frequently Asked Questions about check-code-complete

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

FAQPage Schema

How do I scan my repository for incomplete code before a merge?▼

To scan source files for incomplete code patterns, run an automated detection command in your repository root or specified path. It reports unfinished work markers and dead code with file:line references to streamline remediation.

What are common indicators of unfinished work to look for during static analysis?▼

Common indicators of unfinished work found via static analysis include TODO:, FIXME:, HACK:, and XXX: markers. It also flags empty functions, incomplete implementations, and unused or legacy code blocks in source files.

How do I detect dead code and stray debug artifacts in my source files?▼

Detecting dead code and stray debug artifacts requires scanning source files for unused or legacy code blocks. The scan targets the current directory or specified path to identify leftover artifacts that prevent code from being merge-ready.

Can I limit the scope of a code review scan to a specific directory path?▼

Yes, you can limit the scope of a code review scan by pointing the command at a specific path instead of running it in the repository root. This tailors the incomplete code detection to target only the desired directory.

What is the best way to prevent merging code with empty functions and TODO markers?▼

The best way to prevent merging code with empty functions and TODO markers is automating detection of these patterns as part of your workflow. This surfaces issues with file:line references so you can resolve them before merging.

Related Skills

Explore More Software Engineering Skills→

repository-navigator

Map unfamiliar repositories to relevant files and implementation paths.

project-orchestrator:spec-reviewer

Verify source code implementations against task specifications with file:line references.

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

ck:code-review

Review diffs, commits, and pull requests for security and correctness issues.