Codex Build an Evidence-Based Technical Debt Register
Scan a repository or summarize an existing debt register with impact, frequency, effort, and follow-up evidence.
中文Install in Codex
Use a local repository and an existing register or a fictional fixture with clear context.
- Copy the pinned `.agents/skills/tech-debt/` directory into `.agents/skills/tech-debt/` in the project.
- Choose `$tech-debt scan` or `$tech-debt report` in Codex and provide the intended directory scope.
Example task
Scan a local demo for duplicate date formatting and stale instructions. Record impact, scope, estimated effort, and a review date for each.What to check
Code duplication and stale docs land in the appropriate categories. Each finding cites a file and suggests a next step.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should every FIXME be repaired immediately?
Check whether the problem still exists, who it affects, and whether another task covers it before logging or fixing it.