dead-code-after-removal-sweep

Use after deleting a feature, function, component, validation rule, config flag, enum value, or any symbol — to find the downstream artifacts the deletion orphaned. Covers orphaned string keys in object/label/i18n maps, dead branches, now-unused imports/props, stale comments, and test fixtures that ESLint and code review miss. Trigger when you removed code and want a clean, zero-dead-code diff.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable checklist with concrete grep/lint commands and a clear sequenced workflow including validation steps. It could be tightened by trimming narrative prose and adding an explicit post-sweep verification gate.

Suggestions

Trim narrative padding in the Overview (e.g. "it just sits there, quietly wrong...") and condense the ESLint explanation, which covers behavior Claude already knows.

Add an explicit final verification checkpoint to the workflow (e.g. run the test suite and confirm a clean `git diff` after deleting orphans) to close the validation loop for this destructive sweep.

Move the OPS-5882 Real-World Impact anecdote into a brief one-line example or a separate reference file to keep the core sweep lean.

Dimension	Reasoning	Score
Conciseness	Mostly lean and concrete, but the Overview ("it just sits there, quietly wrong, until it confuses the next person") and the "A removal is not 'the definition'" aphorism add narrative padding, and the ESLint no-unused-vars explanation covers ground Claude already knows.	4 / 5
Actionability	Provides concrete, copy-pasteable grep commands (e.g. `grep -rn "team-members" src/ --include=".js" --include=".jsx" \| grep -v "\.test\."`), `bun run lint`, and `git diff main`, plus a concrete classification scheme; minor gap is that example commands are illustration-specific and require token substitution.	4 / 5
Workflow Clarity	A clear five-step sequence with validation checkpoints (step 4 runs lint and reads the diff; step 5 greps tests before deleting an orphan), but lacks an explicit final gate confirming the build/tests pass after the sweep.	4 / 5
Progressive Disclosure	Well-organized single self-contained file (Overview, Why lint isn't enough, numbered Sweep, Quick Reference table, Common Mistakes, Real-World Impact) with no nested references and easy navigation via the table; slightly over the simple-skill line length and the Real-World Impact anecdote is borderline inline material.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that clearly states what it does and when to use it, with a distinctive niche and good trigger coverage. The only minor gap is a few natural synonyms a user might voice when requesting this kind of cleanup.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete orphan classes the sweep targets — "orphaned string keys in object/label/i18n maps, dead branches, now-unused imports/props, stale comments, and test fixtures" — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (find downstream orphaned artifacts: string keys, dead branches, imports/props, stale comments, fixtures) and when ("Trigger when you removed code and want a clean, zero-dead-code diff") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ("after deleting a feature, function, component...", "Trigger when you removed code", "zero-dead-code diff"), but a few common synonyms a user might say (e.g. "unused code", "cleanup after refactor", "leftover") are not present.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — a post-deletion dead-code sweep that explicitly targets what ESLint and review miss — with distinct triggers unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HHS/OPRE-OPS
Path: .claude/skills/dead-code-after-removal-sweep/SKILL.md
Commit: 4ff5a51

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.