tech-debt
Identify, categorize, and prioritize technical debt when assessing maintenance backlog, refactoring priorities, or the cost and risk of deferred work. Keep the assessment within the requested project or component.
- License 许可
- MIT
- 所属仓库
- meymchen/skills
- 最近更新
- 2026-10-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- tech-debt
- description
- Identify, categorize, and prioritize technical debt when assessing maintenance backlog, refactoring priorities, or the cost and risk of deferred work. Keep the assessment within the requested project or component.
- user-invocable
- true
- disable-model-invocation
- false
02 资源文件 1
- 参考文档agents/openai.yaml175 B
03 SKILL.md 正文
<!-- Adapted by Yuming Chen on 2026-10-04 for personal use and dual-host support. See ../../UPSTREAM.md. -->
Tech Debt Management
Read CONNECTORS.md for host invocation, personal use, and optional tools.
Systematically identify, categorize, and prioritize technical debt.
Categories
| Type | Examples | Risk |
|---|---|---|
| Code debt | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
| Architecture debt | Boundaries or data store that no longer fit requirements | Scaling limits |
| Test debt | Low coverage, flaky tests, missing integration tests | Regressions ship |
| Dependency debt | Outdated libraries, unmaintained dependencies | Security vulns |
| Documentation debt | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
| Infrastructure debt | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
Prioritization Framework
Score each item on:
- Impact: How much does it slow the maintainer or team down? (1-5)
- Risk: What happens if we don't fix it? (1-5)
- Effort: How hard is the fix? (1-5, inverted — lower effort = higher priority)
Priority = (Impact + Risk) x (6 - Effort)
Output
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
04 同仓库更多 Skills
cleanup-merged-branch
Safely clean a merged local branch, reproducible worktree caches, and stale local branches before updating the repository default branch.
verify-acceptance-items
Verify a GitHub pull request or GitLab merge request (MR) against the acceptance criteria (验收标准/条件, task-list checkboxes) of the issues it links to, then tick the criteria it proves once the user confirms. Use when asked whether a PR or MR is done or meets its issue, when asked to check off an issue's checkboxes, or right after opening or updating a PR or MR that closes an issue.
update-request-body
Update the title and body of one or more GitHub pull requests or GitLab merge requests (MRs).
commit
Create a Git commit from the current changes.
commit-push-request
Commit current changes, push the branch, and open a GitHub pull request or GitLab merge request (MR).
clean-gone
Remove local Git branches whose upstreams are gone, including associated worktrees.