Tech Debt Tracker
Skill ActiveScan 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.
To help engineering teams systematically identify, prioritize, and track technical debt, improving code quality, development velocity, and system maintainability.
Features
- Automated technical debt scanning
- Debt prioritization using multiple frameworks
- Trend analysis and health scoring
- Code quality metric tracking
- Customizable detection rules
Use Cases
- Use when users mention technical debt, code quality, or refactoring.
- Use for planning cleanup sprints or assessing code health.
- Use for legacy code modernization planning.
- Use for estimating maintenance costs.
Non-Goals
- Automated code fixing.
- Real-time code quality monitoring in IDEs.
- Project management or issue tracking integration beyond reporting.
Invocation
- info:Scoped toolsThe repository contains Python scripts that are executed directly, rather than exposing narrowly scoped tools. While functional, this is less ideal than well-defined API calls.
Code Execution
- warning:ValidationWhile input directories and config files are accepted, the scripts rely heavily on default error handling and do not explicitly show validation or sanitization libraries like Zod or pydantic for arguments.
- warning:Error HandlingThe scripts have some error handling (e.g., for file I/O, syntax errors), but broad 'except Exception' blocks and missing specific error types indicate room for improvement in error categorization and meaningful reporting.
- warning:LoggingThe scripts use print statements for output and error reporting but do not appear to implement a dedicated local audit log for actions, outcomes, or errors.
Errors
- warning:Actionable error messagesError messages are present but could be more actionable. For example, 'Scan failed: {e}' could include more context on the failure root cause and potential remediation.
Installation
First, add the marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install engineering@claude-code-skillsQuality Score
Trust Signals
Similar Extensions
Cleanup Cycles
100Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
PM Skill Iterate
99Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
Migrate Validate
100Validate pending migrations for foreign key consistency, rollback safety, and best practices
Semgrep Rule Creator
100Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.