AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ln 626 Dead Code Pruning Auditor

skill-levnikolaevich-claude-code-skills-ln-626-dead-code-pruning-auditor · by levnikolaevich

Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.

No reviews yet
0 installs
26 views
0.0% view→install

Install

$ agentstack add skill-levnikolaevich-claude-code-skills-ln-626-dead-code-pruning-auditor

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-levnikolaevich-claude-code-skills-ln-626-dead-code-pruning-auditor)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ln 626 Dead Code Pruning Auditor? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> Paths: File paths (references/, ../ln-*) are relative to this skill directory.

Dead Code Pruning Auditor (L3 Worker)

Type: L3 Worker

Specialized worker identifying safe deletion candidates.

Purpose & Scope

  • Audit dead code pruning (Category 9: Low Priority)
  • Find unused imports, variables, functions, commented-out code
  • Emit DELETE_DEAD_CODE, REMOVE_OBSOLETE_COMPAT, or DELETE_COMMENTED_CODE
  • Calculate compliance score (X/10)

Inputs

MANDATORY READ: Load references/audit_worker_core_contract.md. Tool policy: follow host AGENTS.md MCP preferences; load references/mcp_tool_preferences.md and references/mcp_integration_patterns.md only when host policy is absent or MCP behavior is unclear.

Receives contextStore with tech stack, codebase root, output_dir.

Use hex-graph first when export liveness or workspace hotspots materially improve the audit. Use hex-line first for local code reads when available. If MCP is unavailable, unsupported, or not indexed, continue with built-in Read/Grep/Glob/Bash and state the fallback in the report.

Workflow

Detection policy: use two-layer detection (candidate scan, then context verification); load references/two_layer_detection.md only when the verification method is ambiguous.

1) Parse context + output_dir 2) Run dead code detection (Layer 1: linters, grep)

  • Graph-capable projects: For JavaScript, TypeScript/TSX, Python, C#, and PHP, use index_project then bounded audit_workspace(verbosity="minimal", limit=5) as primary detection for unused exports when graph indexing is available. Raise limit only for deliberate drill-down.
  • Keep grep/linter fallback for unsupported languages, graph-unavailable runs, and checks outside export liveness.

3) Analyze context per candidate (Layer 2):

  • Unused functions: used via dynamic import/reflection? Exported in public API? Used in other packages (monorepo)?
  • Commented code: TODO with context or algorithm explanation -> FP. Truly dead code block -> confirmed
  • Legacy shims: read git blame -- age? Is there an issue/PR tracking removal?

4) Collect confirmed findings 5) Calculate score 6) Write Report: Build full markdown report in memory per references/templates/audit_worker_report_template.md, write to {output_dir}/ln-626--global.md in single Write call 7) Return Summary: Return minimal summary

Audit Rules

MANDATORY READ: Load references/clean_code_checklist.md for universal dead code patterns and severity definitions.

1. Unreachable Code

Detection:

  • Linter rules: no-unreachable (ESLint)
  • Check code after return, throw, break

Severity: MEDIUM

2. Unused Imports/Variables/Functions

Detection:

  • ESLint: no-unused-vars
  • TypeScript: noUnusedLocals, noUnusedParameters
  • Python: flake8 with F401, F841

Severity:

  • MEDIUM: Unused functions (dead weight)
  • LOW: Unused imports (cleanup needed)

3. Commented-Out Code

Detection:

  • Grep for //.*{ or /*.*function patterns
  • Large comment blocks (>10 lines) with code syntax

Severity: LOW

Recommendation: Delete (git preserves history)

4. Legacy Code & Backward Compatibility

What: Backward compatibility shims, unsupported patterns, old code that should be removed

Detection:

  • Renamed variables/functions with old aliases:
  • Pattern: const oldName = newName or export { newModule as oldModule }
  • Pattern: function oldFunc() { return newFunc(); } (wrapper for backward compatibility)
  • Unsupported exports/re-exports:
  • Grep for // DEPRECATED, @obsolete JSDoc tags
  • Pattern: export.*as.*old.* or export.*legacy.*
  • Conditional code for old versions:
  • Pattern: if.*legacy.* or if.*old.*version.* or isOldVersion ? oldFunc() : newFunc()
  • Migration shims and adapters:
  • Pattern: migrate.*, Legacy.*Adapter, .*Shim, .*Compat
  • Comment markers:
  • Grep for // backward compatibility, // legacy support, // TODO: remove in v
  • Grep for // old implementation, // unsupported, // kept for backward

Severity:

  • HIGH: Backward compatibility shims in critical paths (auth, payment, core features)
  • MEDIUM: Unsupported exports still in use, migration code from >6 months ago
  • LOW: Recent migration code (6 months = MEDIUM, 4h
  • Exclusions: Skip generated code, vendor, migrations, test fixtures
  • Git-aware: Recommend deletion confidently -- git history preserves old code
  • Unique angle: Audit safe deletion candidates only. Do not refactor live code, restructure modules, or assess dependency/package health.
  • Action required: Every finding uses DELETE_DEAD_CODE, REMOVE_OBSOLETE_COMPAT, or DELETE_COMMENTED_CODE.

Definition of Done

Apply the already-loaded references/audit_worker_core_contract.md.

  • [ ] contextStore parsed (including output_dir)
  • [ ] All 4 checks completed (unreachable code, unused imports/vars/functions, commented-out code, legacy shims)
  • [ ] Clean code checklist loaded from references/clean_code_checklist.md
  • [ ] Findings collected with severity, location, effort, action, recommendation
  • [ ] Score calculated per references/audit_scoring.md
  • [ ] Report written to {output_dir}/ln-626--global.md (atomic single Write call)
  • [ ] Summary written per contract

Version: 3.0.0 Last Updated: 2025-12-23

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.