techdebt
Review a code diff / branch / PR for technical debt — code duplication, unnecessary complexity / over-engineering, and redundant or dead code. Use whenever the user wants a tech-debt, cleanup, or refactor review, asks to check a branch or PR for duplication / complexity / dead code before opening a PR, or mentions "techdebt". Refactor-only: it reports issues and offers behavior-preserving fixes; it never changes behavior.
来源信息
- 仓库
- DataDog/dd-trace-java
- 最近来源活动
- 2026年7月22日 11:26
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 738
- Forks
- 364
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- techdebt
- description
- Review a code diff / branch / PR for technical debt — code duplication, unnecessary complexity / over-engineering, and redundant or dead code. Use whenever the user wants a tech-debt, cleanup, or refactor review, asks to check a branch or PR for duplication / complexity / dead code before opening a PR, or mentions "techdebt". Refactor-only: it reports issues and offers behavior-preserving fixes; it never changes behavior.
- user-invocable
- true
- context
- fork
- allowed-tools
- ["Bash","Read","Grep","Glob"]
# Techdebt Cleanup Skill
Analyze changes on the current branch to identify and fix technical debt, code duplication, and unnecessary complexity.
## Instructions
### Step 1: Get Branch Changes
Find the merge-base (where this branch diverged from master) and compare against it:
```bash
# Find upstream (DataDog org repo)
UPSTREAM=$(git remote -v | grep -E 'DataDog/[^/]+(.git)?\s' | head -1 | awk '{print $1}')
if [ -z "$UPSTREAM" ]; then
echo "No DataDog upstream found, using origin"
UPSTREAM="origin"
fi
# Find the merge-base (commit where this branch diverged from master)
MERGE_BASE=$(git merge-base HEAD ${UPSTREAM}/master)
echo "Comparing changes introduced on this branch since diverging from master using base commit: $MERGE_BASE"
git diff $MERGE_BASE --stat
git diff $MERGE_BASE --name-status
```
If no changes exist, inform the user and stop.
If changes exist, read the diff and the full content of modified source files (not test files) to understand context.
### Step 2: Analyze for Issues
Look for:
**Code Duplication**
- Similar code blocks that should be extracted into shared functions
- Copy-pasted logic with minor variations
**Unnecessary Complexity**
- Over-engineered solutions (abstractions used only once)
- Excessive indirection or layers
- Backward compatibility shims that aren't needed
**Redundant Code**
- Dead code paths
- Overly defensive checks for impossible scenarios
### Step 3: Report and Fix
Present a concise summary of issues found with file:line references.
Then ask the user if they want you to fix the issues. When fixing:
- Make one logical change at a time
- Do NOT change behavior, only refactor
- Skip trivial or stylistic issues
在 GitHub 查看