audit-dead-code-auditor-references-checklist

Loads a YAML-described skill entrypoint and produces category-based dead-code review guidance from canonical references.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill audit-dead-code-auditor-references-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-dead-code-auditor-references-checklist
Source: https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production/tree/main/.claude/skills/audit-dead-code-auditor-references-checklist
Command: npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill audit-dead-code-auditor-references-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify likely dead code by giving a structured, category-based checklist you can apply during code audits.

Core Features & Use Cases

  • Category-based dead-code detection: Provides a checklist organized by common patterns so reviews stay consistent.
  • Reference-canonical guidance: Points to the canonical reference document so you can follow the authoritative instructions for your audit workflow.
  • Use Case: When refactoring a large codebase, run through each checklist category to spot unused functions, unreachable branches, or obsolete modules before they accumulate technical debt.

Quick Start

Use the audit-dead-code-auditor-references-checklist reference checklist document to guide your dead-code audit pass for your target repository.

Frequently Asked Questions about audit-dead-code-auditor-references-checklist

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

FAQPage Schema
How do I identify dead code during a source code refactor?

To identify dead code during a source code refactor, apply a category-based checklist to consistently review patterns like unused functions, unreachable branches, and obsolete modules before technical debt accumulates.

What is a category-based checklist for dead code detection?

A category-based checklist for dead code detection is a structured review tool that organizes common source code patterns, ensuring consistent static review passes when identifying unused or unreachable logic during maintenance.

Can I use a static review checklist to reduce technical debt in a large codebase?

Yes, you can use a static review checklist to reduce technical debt in a large codebase by running through each category to systematically spot unused functions and obsolete modules during maintenance.

What's the best way to find unreachable branches and obsolete modules during code audits?

The best way to find unreachable branches and obsolete modules during code audits is replacing ad-hoc intuition with a repeatable category-based checklist that guides static reviews across common code patterns.

When do I need a structured checklist for dead code detection?

You need a structured checklist for dead code detection when relying on ad-hoc intuition fails, specifically during refactors, maintenance, and technical-debt reduction in source code repositories.