Install
$ agentstack add skill-philoserf-claude-code-config-tech-debt ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Technical Debt Analysis
Systematic methodology for identifying, classifying, and prioritizing technical debt across a codebase. This skill diagnoses — it produces an inventory and remediation roadmap but does not modify code.
When to Use
- User asks about technical debt, maintenance burden, or "what's slowing us down"
- Starting a new engagement with an unfamiliar codebase
- Before a major refactor to scope and prioritize work
- Periodic health check on code quality
Workflow
1. Scan
Walk the codebase and identify debt items using the [debt categories](references/debt-categories.md).
- Glob for project structure and file sizes
- Grep for known smell patterns (TODO/FIXME/HACK, deeply nested code, large files)
- Read representative files in hotspot areas
- Classify each finding into its debt category
Scaling by codebase size:
| Files | Strategy | | ------ | -------------------------------------------------------------------------------------- | |
- Scope:
Debt Items
| # | Category | Item | Location | Risk | Effort | Tier | |---|----------|------|----------|------|--------|------| | 1 | Code | ... | ... | ... | ... | ... |
Prioritized Roadmap
Quick Wins
- [items with rationale]
Medium-Term
- [items with rationale]
Long-Term
- [items with rationale]
Recommendations
- [key observations and suggested next steps]
## Output Format
1. **Debt Inventory** — Categorized list with locations, risk levels, and effort estimates
2. **Prioritized Roadmap** — Action tiers with rationale for ordering
3. **Recommendations** — Sequencing and scoping advice (what to tackle first and why). Diagnosis and prioritization, not implementation steps.
## Reference Files
Detailed taxonomy and scoring guidance:
- [debt-categories.md](references/debt-categories.md) — Debt types with detection criteria and measurement thresholds
- [roi-framework.md](references/roi-framework.md) — Impact assessment, risk classification, and prioritization tiers
## Do not use when
- Finding specific bugs with file:line precision — use `code-audit`
- Reviewing a specific staged or branch diff — use `diff-review`
- Auditing dependency health specifically — use `deps-audit`
- Performance profiling without structural concerns
- Single-file code review
## Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- **Author:** [philoserf](https://github.com/philoserf)
- **Source:** [philoserf/claude-code-config](https://github.com/philoserf/claude-code-config)
- **License:** MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.