quality-checkThis skill should be used when the user asks to "check code quality", "score this code", "find quality hotspots", "prioritize refactoring", "analyze technical debt", "run CodeDNA", or assess maintainability, complexity, modularity, tests, documentation, and best practices.
Independent GitHub snapshot · Automated classification · Original documentation governs
Codex CLI: Invoke when the description matches, or manually with
$quality-check. No hooks or background auto-run.
Automatically invoke this Skill when:
CodeDNA Quality Analyzer provides:
When this Skill is invoked:
Ask yourself:
test_quality_simple.pyproject_quality_analyzer.py --mode overviewproject_quality_analyzer.py --mode impact-analysisIMPORTANT: Execute one of these analyzer commands. Prefer python3, fall
back to python, and allow PROJECTMIND_HOME to override the default local
tool path.
Single File Analysis:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
if [ -z "$PYTHON_BIN" ]; then
echo "CodeDNA error: no python3 or python interpreter found" >&2
exit 1
fi
"$PYTHON_BIN" "$PROJECTMIND_HOME/test_quality_simple.py" "[file_path]"
Project Overview:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
if [ -z "$PYTHON_BIN" ]; then
echo "CodeDNA error: no python3 or python interpreter found" >&2
exit 1
fi
"$PYTHON_BIN" "$PROJECTMIND_HOME/project_quality_analyzer.py" --project "[directory_path]" --mode overview
Impact Analysis:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
if [ -z "$PYTHON_BIN" ]; then
echo "CodeDNA error: no python3 or python interpreter found" >&2
exit 1
fi
"$PYTHON_BIN" "$PROJECTMIND_HOME/project_quality_analyzer.py" --file "[file_path]" --mode impact-analysis
If $PYTHON_BIN is empty, report that no Python interpreter was found and fall
back to direct local inspection with rg, rg --files, targeted reads, and the
repo's own test/lint commands.
Format the output as:
## 🔬 Code Quality Analysis
**Target**: [File/Project Path]
**Overall Score**: XX/100 [🟢/🟡/🔴]
### 6-Dimension Breakdown
| Dimension | Score | Status | Key Insights |
|-----------|-------|--------|--------------|
| Complexity | XX/100 | 🟢/🟡/🔴 | [Main issue] |
| Maintainability | XX/100 | 🟢/🟡/🔴 | [Main issue] |
| Modularity | XX/100 | 🟢/🟡/🔴 | [Main issue] |
| Test Coverage | XX/100 | 🟢/🟡/🔴 | [Main issue] |
| Documentation | XX/100 | 🟢/🟡/🔴 | [Main issue] |
| Best Practices | XX/100 | 🟢/🟡/🔴 | [Main issue] |
### 🔴 Critical Issues (Fix Immediately)
1. **[Issue Name]** - [File:Line]
- Impact: [High/Medium/Low]
- Explanation: [What's wrong]
- Fix: [Specific solution]
### 🟡 Important Issues (Fix This Sprint)
1. **[Issue Name]** - [File:Line]
- Impact: [explanation]
- Suggested approach: [how to fix]
### 💡 Refactoring Priorities (ROI-Optimized)
Based on PageRank and quality analysis:
1. **[Module/File Name]** (ROI: High)
- Current Score: XX/100
- Effort: [X hours]
- Benefit: [Specific improvements]
- Priority: P0/P1/P2
2. **[Module/File Name]** (ROI: Medium)
- [Details...]
### 📊 Quality Hotspots
Files that would benefit most from refactoring:
- [File 1]: Score XX, high dependency count
- [File 2]: Score XX, complex and frequently changed
- [File 3]: Score XX, critical business logic
### 🎯 Recommended Actions
**Immediate (This Week)**:
- [ ] [Specific action with file:line]
- [ ] [Specific action with file:line]
**Short-term (This Sprint)**:
- [ ] [Refactoring task]
- [ ] [Testing improvement]
**Long-term (Next Quarter)**:
- [ ] [Architecture improvement]
- [ ] [Technical debt reduction]
Explain:
User: "Check the quality of src/auth/login.ts"
Execute:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
"$PYTHON_BIN" "$PROJECTMIND_HOME/test_quality_simple.py" src/auth/login.ts
You present: 6-dimension scores, specific issues, and refactoring suggestions.
User: "How's the code quality of my payment module?"
Execute:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
"$PYTHON_BIN" "$PROJECTMIND_HOME/project_quality_analyzer.py" --project src/payment --mode overview
You present: Project-wide quality assessment, hotspots, and priority fixes.
User: "I want to refactor the database layer, what's the impact?"
Execute:
PROJECTMIND_HOME="${PROJECTMIND_HOME:-/Users/WangQiao/claude-enhanced-quality}"
PYTHON_BIN="${PYTHON_BIN:-$(command -v python3 || command -v python || true)}"
"$PYTHON_BIN" "$PROJECTMIND_HOME/project_quality_analyzer.py" --file src/core/database.ts --mode impact-analysis
You present: Dependency analysis, affected files, risk assessment, and refactoring plan.
Scoring system:
Refactoring priority is based on:
For project-level analysis, the system uses:
/Users/WangQiao/claude-enhanced-quality
or another path supplied through PROJECTMIND_HOME