dead-code-review

Name: dead-code-review
Availability: InStock
Author: exerias21

Guide a six-phase sequential review to identify and remove dead code.

Updated Apr 18, 2026

Search Tags:#testing #refactor #quality-assurance #code-review #copilot #dead-code

Ready to run

npx skills add https://github.com/exerias21/brainstorm-toolkit --skill dead-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dead-code-review
Source: https://github.com/exerias21/brainstorm-toolkit/tree/main/copilot/skills/dead-code-review
Command: npx skills add https://github.com/exerias21/brainstorm-toolkit --skill dead-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines code cleanup by guiding a structured, six-phase dead-code review for Copilot-powered workflows, helping teams identify and remove dead or unsafe code after major features or refactors.

Core Features & Use Cases

Six sequential phases (backend, frontend, database, docs, scripts, tests) executed in order to avoid parallel conflicts.
Test baseline phase to measure impact and prevent regression.
Triage findings with clear criteria and guided removal steps.
Use case: after a feature release or refactor; ensures code health before release.

Quick Start

Invoke the sequential dead-code-review workflow after a major feature to start the six-phase cleanup and verification process.

Frequently Asked Questions about dead-code-review

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

FAQPage Schema

How do I identify and remove dead code after a major feature release?▼

To identify and remove dead code after a feature release, use a structured six-phase sequential review covering backend, frontend, database, docs, scripts, and tests to safely eliminate unused code and risky patterns.

What is the best way to prevent regressions during a dead code cleanup?▼

The best way to prevent regressions during dead code cleanup is to enforce a test baseline phase before removal, measuring impact and verifying the test plan sequentially across all repository layers.

How does a sequential code review workflow handle multi-file refactors?▼

A sequential code review workflow handles multi-file refactors by executing staged backend and frontend analysis in order, avoiding parallel conflicts while applying triage rules and safe fallback guidance to ensure code health.

Can I use Copilot to guide database and documentation cleanup alongside backend code?▼

Yes, you can use Copilot to guide database and documentation cleanup alongside backend code by running a structured review that includes dedicated phases for database checks, documentation reviews, and script hygiene.

When should I perform a post-merge dead code review?▼

You should perform a post-merge dead code review after major feature launches or multi-file refactors to ensure code health before release, using staged analysis and triage rules to safely remove unused code.