gap-check

Audit code quality gaps and dead code in recent changes.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/vatsal2210/claude-skills --skill gap-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-check
Source: https://github.com/vatsal2210/claude-skills/tree/main/gap-check
Command: npx skills add https://github.com/vatsal2210/claude-skills --skill gap-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a feature or fix is implemented, developers often miss quality gaps or leave behind unused files, leading to bugs, technical debt, and harder maintenance. This skill performs a focused post‑implementation audit to surface those hidden issues.

Core Features & Use Cases

  • Quality‑gap analysis across six categories such as incomplete paths, missing error handling, and race conditions.
  • Dead‑code detection across five categories including unused files, stale imports, and leftover debug code.
  • Scoped reviews for code, documentation, or shell/infra changes based on git diffs, session edits, or explicit user input.
  • Structured report with severity labels (Critical, Should fix, Minor), dead‑code listings, and a final verdict.

Quick Start

Ask the gap‑check skill to review the recent changes in my project.

Frequently Asked Questions about gap-check

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

FAQPage Schema
How do I audit my codebase for dead code and quality gaps after implementation?

Dead code detection scans codebases, documentation, and shell scripts to identify unused files, stale imports, and leftover debug code. It categorizes these unused elements across five specific dead-code categories to help reduce technical debt and maintenance overhead.

Can I review uncommitted git diffs for missing error handling and race conditions?

Quality-gap analysis covers six categories including incomplete paths, missing error handling, and race conditions. It evaluates scoped reviews of code, documentation, or shell scripts based on git diffs, session edits, or explicitly specified user files to surface hidden bugs.

What is the best way to detect leftover debug code and stale imports in shell scripts?

Post-implementation audits support codebases, documentation, and shell or infrastructure scripts. Users can scope reviews by providing explicit file inputs, analyzing uncommitted diffs, or targeting recent session edits to identify hidden bugs and unused files.

What are the limitations of automated dead code and quality gap detection?

Limitations of automated dead code and quality gap detection include relying on the scope of provided git diffs, session edits, or specified files. The audit produces severity labels and a verdict, but users must manually resolve the identified technical debt and hidden bugs.