skills.rest
dmooney
dmooneyCOMMUNITY
Explore all skills by this author →
GitHub

techdebt

Reduce Rust workspace technical debt by processing TODO.md items and verifying fixes.

Updated Mar 18, 2026
Search Tags:#technical debt#module splitting#cargo clippy#crate audit#rust workspace#TODO triage#refactor PR
One-click install
npx skills add https://github.com/dmooney/Rundale --skill techdebt-dmooney
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/techdebt
Command: npx skills add https://github.com/dmooney/Rundale --skill techdebt-dmooney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reduce accumulating technical debt in a Rust workspace by turning vague “we should refactor this” notes into trackable, verified fixes and behavior-preserving structural audits.

Core Features & Use Cases

  • Continuous TODO.md debt sweeper: Loads or initializes a TODO.md list, discovers additional credible debt, and dispatches focused fix agents until the list is empty.
  • Crate-layout audit refactor: Produces a shippable, behavior-preserving refactor PR that standardizes crate naming, Cargo.toml metadata, splits oversized modules, and evaluates extraction candidates.
  • Safety and verification gates: Enforces clean baseline checks, “no mixed fixes,” and repository hygiene gates (fmt/clippy/tests, stale reference grep).

Use cases: ongoing debt cleanup in the parish/ Rust workspace, and structured workspace reorganization when crate sprawl makes maintenance slow or error-prone.

Quick Start

Run techdebt in the folder you want to clean so it scopes debt discovery and fix dispatch to that directory.

Frequently Asked Questions about techdebt

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

FAQPage Schema
How do I automate technical debt cleanup in a Rust workspace?▼

You can automate Rust technical debt cleanup by consuming TODO.md work items and iteratively dispatching agents to fix credible issues. The process enforces strict refactor and bug separation alongside verification gates for builds, tests, and clippy checks.

What is a behavior-preserving refactor PR for Rust crates?▼

A behavior-preserving refactor PR restructures Rust crates by standardizing naming, updating Cargo.toml manifests, splitting oversized modules, and evaluating extraction candidates without altering existing runtime behavior.

How do I split oversized Rust modules safely?▼

To split oversized Rust modules safely, generate a behavior-preserving refactor PR that restructures the crate layout. This enforces clean baseline checks, clippy, and stale-reference greps to validate module extraction without breaking dependencies.

Does technical debt refactoring require separating bug fixes from structural changes?▼

Yes, strict refactor and bug separation is required during technical debt cleanup. This no-mixed-fixes constraint ensures structural changes like module splits remain behavior-preserving and pass verification gates for builds, tests, and stale-reference checks.

When do I need a crate-layout audit for Rust?▼

You need a Rust crate-layout audit when crate sprawl makes maintenance slow or error-prone. The audit produces a refactor PR that standardizes naming, updates manifests, splits modules, and evaluates extraction candidates to restore workspace maintainability.

Related Skills

Explore More Software Engineering Skills→
brolagbrolag
11

todo-new

Generate a structured todo.md with phases, tasks, and completion criteria.

Community
Intermediate
coralogixcoralogix
114

run-tests

Run cargo test, fmt, and clippy for the cx CLI codebase.

Official
Intermediate
parumaparuma
1

code-verifier

Run Rust verification suite with tests, coverage, formatting, clippy, and snippets.

Community
Advanced
NickCrewNickCrew
29

terraform-best-practices

Guide Terraform infrastructure-as-code with modular design and secure state management.

Community
Intermediate