원클릭으로 Manus에서 모든 스킬 실행

doncheli-tech-debt

스타56

포크10

업데이트2026년 4월 1일 17:09

Identify, quantify, and prioritize technical debt in the codebase. Activate when user mentions "tech debt", "code quality", "technical debt", "code smells", "refactor candidates", "what to clean up".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

doncheli

doncheli/don-cheli-sdd

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Don Cheli: Tech Debt Scanner

Instructions

Scan the codebase for tech debt signals:
- TODO/FIXME/HACK/XXX comments with file and line
- Functions exceeding cyclomatic complexity of 10
- Files exceeding 300 lines (configurable)
- Duplicated code blocks (> 10 lines repeated 3+ times)
- Deprecated dependencies or APIs in use
- Missing error handling (uncaught exceptions, empty catch blocks)
- Test files that exist but have 0 assertions
Score each item by impact (high/medium/low) and effort (hours estimate)
Compute a Tech Debt Ratio: debt items / total files
Prioritize using the impact/effort matrix: Quick Wins first, then High Impact
Recommend a remediation plan with a suggested order
Never auto-refactor — produce the plan and wait for approval
Save the report to .dc/tech-debt-<date>.md

Output Format

## Tech Debt Report — 2026-03-28

### Summary
- Total debt items: 18
- Tech Debt Ratio: 18/94 files = 19% (target: <10%)
- Estimated remediation effort: ~14h

### Quick Wins (high impact, low effort)
1. src/utils/format.ts — 3 duplicate date-format blocks — 1h — extract to shared util
2. src/auth/token.ts:88 — empty catch block silently swallows JWT errors — 30m fix

### High Impact (high impact, higher effort)
1. src/payments/processor.ts — cyclomatic complexity 18 — 4h refactor

### Low Priority
1. 7 TODO comments in src/legacy/ — document or schedule removal

### Remediation Plan
Sprint 1 (8h): Quick wins + empty catch blocks
Sprint 2 (6h): payments/processor.ts refactor
Backlog: legacy TODOs

이 저장소의 다른 Skills

같은 저장소

doncheli-prd

doncheli/don-cheli-sdd

Generate professional Product Requirement Documents (PRD) from multiple sources — Figma designs, briefs, user research, existing code. Includes risk analysis, RICE prioritization, Gherkin stories and launch plan. Activate when user mentions "PRD", "product requirements", "requirement document", "product spec", "figma to PRD", "generate PRD".

2026-04-0756

doncheli-audit-trail

doncheli/don-cheli-sdd

Record and query the decision log for a project. Activate when user mentions "audit", "trail", "log decisions", "decision history", "why was this decided", "ADR", "architecture decision".

2026-04-0156

doncheli-data-policy

doncheli/don-cheli-sdd

Audit and document what personal or sensitive data the project collects, processes, and stores. Activate when user mentions "privacy", "data policy", "what data", "GDPR", "personal data", "data retention", "PII".

2026-04-0156

doncheli-drift

doncheli/don-cheli-sdd

Detect and reconcile divergence between specs and implementation. Activate when user mentions "drift", "sync", "spec divergence", "out of sync", "spec doesn't match", "implementation differs".

2026-04-0156

doncheli-estimate

doncheli/don-cheli-sdd

Estimate effort, duration and cost using 4 complementary models (Function Points, Planning Poker AI, COCOMO, Historical). Activate when user mentions "estimate", "estimation", "effort", "how long", "cost", "story points", "sizing".

2026-04-0156

doncheli-spec-score

doncheli/don-cheli-sdd

Evaluate the quality of a spec and return a structured score with improvement recommendations. Activate when user mentions "spec quality", "score spec", "how good is my spec", "spec review", "validate spec quality".

2026-04-0156

name	doncheli-tech-debt
description	Identify, quantify, and prioritize technical debt in the codebase. Activate when user mentions "tech debt", "code quality", "technical debt", "code smells", "refactor candidates", "what to clean up".

Don Cheli: Tech Debt Scanner

Instructions

Scan the codebase for tech debt signals:
- TODO/FIXME/HACK/XXX comments with file and line
- Functions exceeding cyclomatic complexity of 10
- Files exceeding 300 lines (configurable)
- Duplicated code blocks (> 10 lines repeated 3+ times)
- Deprecated dependencies or APIs in use
- Missing error handling (uncaught exceptions, empty catch blocks)
- Test files that exist but have 0 assertions
Score each item by impact (high/medium/low) and effort (hours estimate)
Compute a Tech Debt Ratio: debt items / total files
Prioritize using the impact/effort matrix: Quick Wins first, then High Impact
Recommend a remediation plan with a suggested order
Never auto-refactor — produce the plan and wait for approval
Save the report to .dc/tech-debt-<date>.md

Output Format

## Tech Debt Report — 2026-03-28

### Summary
- Total debt items: 18
- Tech Debt Ratio: 18/94 files = 19% (target: <10%)
- Estimated remediation effort: ~14h

### Quick Wins (high impact, low effort)
1. src/utils/format.ts — 3 duplicate date-format blocks — 1h — extract to shared util
2. src/auth/token.ts:88 — empty catch block silently swallows JWT errors — 30m fix

### High Impact (high impact, higher effort)
1. src/payments/processor.ts — cyclomatic complexity 18 — 4h refactor

### Low Priority
1. 7 TODO comments in src/legacy/ — document or schedule removal

### Remediation Plan
Sprint 1 (8h): Quick wins + empty catch blocks
Sprint 2 (6h): payments/processor.ts refactor
Backlog: legacy TODOs