throatee

Analyze Rust workspace call graphs and compiler warnings to identify unused code.

2|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Impractical-Instruments/reuben --skill throatee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: throatee
Source: https://github.com/Impractical-Instruments/reuben/tree/main/.claude/skills/throatee
Command: npx skills add https://github.com/Impractical-Instruments/reuben --skill throatee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of technical debt by identifying code that is no longer in use or can be significantly simplified, preventing the codebase from becoming bloated and unmaintainable.

Core Features & Use Cases

  • Dead Code Detection: Identifies production code that lacks callers or is only referenced by tests.
  • Simplification Analysis: Highlights opportunities to remove needless indirection, duplication, and dead configuration knobs.
  • Use Case: Use this skill during a refactoring sprint to generate a prioritized report of modules that can be safely deleted or collapsed to improve system performance and developer velocity.

Quick Start

Invoke the throatee skill to audit the current workspace and generate a report of potential deletions and simplifications.

Frequently Asked Questions about throatee

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

FAQPage Schema
Does dead code detection work with compiler warnings to find needless code indirection?

Dead code detection works with compiler warnings and call graph analysis to find needless code indirection. It highlights opportunities to remove duplication and dead configuration knobs within a Rust workspace to improve developer velocity.

How do I find unused code in a Rust workspace to reduce technical debt?

To find unused code in a Rust workspace, you can audit call graphs and compiler warnings to identify production code lacking callers. This generates an impact-ranked report of vestigial modules for safe deletion.

What is the best way to identify dead code that is only referenced by tests?

Identifying dead code referenced only by tests involves analyzing call graphs to distinguish active logic from vestigial production code. This simplification analysis highlights needless indirection and dead configuration knobs for removal.

How do I generate a prioritized report for Rust code simplification during a refactoring sprint?

You generate a prioritized report for Rust code simplification by invoking an audit that analyzes call graphs and compiler warnings. This provides impact-ranked recommendations for deleting or collapsing modules without automated modifications.

Can I use an automated code cleanup tool to directly refactor complex Rust modules?

You cannot use this audit approach to directly refactor complex Rust modules, as it provides recommendations for deletion and simplification without performing automated modifications. It reports unused or overly complex code segments to reduce technical debt.

Does dead code detection work with compiler warnings to find needless code indirection?

Dead code detection works with compiler warnings and call graph analysis to find needless code indirection. It highlights opportunities to remove duplication and dead configuration knobs within a Rust workspace to improve developer velocity.