Techdebt
- 51 installs
- 590 repo stars
- Updated June 23, 2026
- meleantonio/awesome-econ-ai-stuff
Helps with ai & agent building tasks.
About
techdebt is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- techdebt
- AI & Agent Building
- AI-coding skill
Techdebt by the numbers
- 51 all-time installs (skills.sh)
- +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #7,219 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/meleantonio/awesome-econ-ai-stuff --skill techdebtAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 51 |
|---|---|
| repo stars | ★ 590 |
| Last updated | June 23, 2026 |
| Repository | meleantonio/awesome-econ-ai-stuff ↗ |
What it does
Helps with ai & agent building tasks.
Files
Technical Debt Finder
Identify and fix technical debt in the codebase.
What to Look For
Code Duplication
- Functions with similar logic that could be consolidated
- Copy-pasted code blocks
- Repeated patterns that should be abstracted
Dead Code
- Unused imports
- Unused functions or classes
- Commented-out code blocks
- Unreachable code paths
Outdated Patterns
- Deprecated API usage
- Old-style string formatting (% or .format) vs f-strings
- Type hints using
typing.Listinstead oflist - Missing type hints on public functions
Code Smells
- Functions longer than 50 lines
- Too many parameters (more than 5)
- Deep nesting (more than 3 levels)
- Magic numbers without constants
- Overly complex conditionals
Missing Best Practices
- Missing docstrings on public functions
- Missing error handling
- Hardcoded values that should be config
- Missing tests for critical paths
Workflow
1. Scan the Codebase
- Look for patterns matching the issues above
- Prioritize by impact and ease of fix
2. Report Findings
- List issues by category
- Include file paths and line numbers
- Estimate severity (high/medium/low)
3. Fix Issues
- Start with high-severity, easy fixes
- Create atomic commits for each fix
- Run tests after each change
4. Verify
- Run linter:
ruff check . - Run tests:
pytest - Ensure no new issues introduced
Arguments
Optionally specify a directory or file to focus on.
Usage:
/techdebt- Scan entire project/techdebt src/- Scan specific directory/techdebt src/utils.py- Scan specific file
Output
Provide a summary of:
- Issues found (by category)
- Issues fixed
- Remaining items for future sessions
Technical Debt Finder
Identify and fix technical debt in the codebase.
What to Look For
Code Duplication
- Functions with similar logic that could be consolidated
- Copy-pasted code blocks
- Repeated patterns that should be abstracted
Dead Code
- Unused imports
- Unused functions or classes
- Commented-out code blocks
- Unreachable code paths
Outdated Patterns
- Deprecated API usage
- Old-style string formatting (% or .format) vs f-strings
- Type hints using
typing.Listinstead oflist - Missing type hints on public functions
Code Smells
- Functions longer than 50 lines
- Too many parameters (more than 5)
- Deep nesting (more than 3 levels)
- Magic numbers without constants
- Overly complex conditionals
Missing Best Practices
- Missing docstrings on public functions
- Missing error handling
- Hardcoded values that should be config
- Missing tests for critical paths
Workflow
1. Scan the Codebase
- Look for patterns matching the issues above
- Prioritize by impact and ease of fix
2. Report Findings
- List issues by category
- Include file paths and line numbers
- Estimate severity (high/medium/low)
3. Fix Issues
- Start with high-severity, easy fixes
- Create atomic commits for each fix
- Run tests after each change
4. Verify
- Run linter:
ruff check . - Run tests:
pytest - Ensure no new issues introduced
Arguments
Optionally specify a directory or file to focus on.
Usage:
/techdebt- Scan entire project/techdebt src/- Scan specific directory/techdebt src/utils.py- Scan specific file
Output
Provide a summary of:
- Issues found (by category)
- Issues fixed
- Remaining items for future sessions
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10AI & Agent Buildingagents