tech-debt-tracker
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/alirezarezvani/tech-debt-trackerWhat This Skill Does
The Tech Debt Tracker is a sophisticated engineering management utility designed to identify, categorize, and prioritize technical debt within complex codebases. Instead of relying on manual oversight, it leverages automated scanners, complexity analysis, and architectural evaluation tools to surface latent issues like code rot, architectural bottlenecks, and maintainability anti-patterns. The skill transforms abstract technical debt into measurable data points using cost-of-delay frameworks. By offering a unified Debt Dashboard, engineering teams can visualize the growth or reduction of technical debt, enabling stakeholders to make informed, data-driven decisions on when to prioritize refactoring versus feature development. It treats technical debt with the same rigor as financial debt, calculating the 'interest' accrued in the form of increased bug rates and slower development velocity.
Installation
To integrate this skill into your environment, use the OpenClaw command-line interface. Run the following command in your terminal:
clawhub install openclaw/skills/skills/alirezarezvani/tech-debt-tracker
Ensure that your OpenClaw agent has appropriate read permissions to your project repository to allow the Debt Scanner to analyze your source code files effectively.
Use Cases
- Sprint Planning: Use the Debt Prioritizer to identify the top 3 highest-impact refactoring tasks that will yield the biggest improvement in development speed for the upcoming sprint.
- Technical Audits: Run the Debt Scanner before a major release to generate a comprehensive report on architectural coupling and cyclomatic complexity to prevent production stability issues.
- Onboarding/Knowledge Transfer: Leverage the Code Debt report to identify 'knowledge silos' or overly complex code modules that require additional documentation or unit tests before new developers begin work.
Example Prompts
- 'Run a scan on the src/api directory and list all functions that exceed 50 lines of code or have a cyclomatic complexity score above 10.'
- 'Analyze the current architecture and identify any circular dependencies that might be slowing down our build times.'
- 'Generate a report comparing our current technical debt metrics against those from three months ago to see if our refactoring efforts are having a net positive impact.'
Tips & Limitations
For the best results, ensure your project follows standard directory structures; the scanner relies on consistent file paths to perform accurate dependency analysis. Note that the Debt Prioritizer is a heuristic tool; while it calculates impact based on complexity and coupling, it cannot perfectly predict business-side priority. Always verify suggested refactors with a senior engineer. The tool works best when run regularly as part of a CI/CD pipeline rather than as a one-time audit, as consistent monitoring allows for better trend analysis over time.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-alirezarezvani-tech-debt-tracker": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, code-execution
Related Skills
agile-product-owner
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.
intl-expansion
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.
mdr-745-specialist
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.
marketing-strategy-pmm
Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
paid-ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.