notque/vexjoy-agent / skills/code-quality/code-quality
code-quality
VerifiedCode quality: cleanup, linting, formatting, quality gates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/biome-rules-reference.md | markdown | 11.1 KB |
| references/cleanup-report-template.md | markdown | 3.1 KB |
| references/cleanup-scan-commands.md | markdown | 5.5 KB |
| references/code-cleanup.md | markdown | 11.8 KB |
| references/pyproject-template.toml | config | 15.4 KB |
| references/python-report-template.md | markdown | 3.1 KB |
| references/python-tool-commands.md | markdown | 4.4 KB |
| references/ruff-rules-reference.md | markdown | 10.0 KB |
| scripts/run_quality_gate.py | script | 2.4 KB |
references/cleanup-report-template.md
View on GitHub# Code Cleanup Report Template
Use this template to structure cleanup scan output. Replace placeholders with actual data.
---
```markdown
# Code Cleanup Report
**Generated**: {timestamp}
**Repository**: {repo_path}
**Languages**: {Python, Go, etc.}
**Scope**: {directories scanned}
**Total Issues**: {N}
---
## Executive Summary
| Tier | Count | Est. Effort |
|------|-------|-------------|
| Quick Wins (High Impact, Low Effort) | {N} | {time} |
| Important (High Impact, Medium+ Effort) | {N} | {time} |
| Polish (Medium/Low Impact) | {N} | {time} |
**Top Recommendations**:
1. {Highest priority type} - {N} instances
2. {Second priority type} - {N} instances
3. {Third priority type} - {N} instances
---
## Quick Wins
### Unused Imports ({N} files)
**Impact**: Medium | **Effort**: Trivial | **Auto-fixable**: Yes
- `{file}:{line}` - `{import}` imported but unused
- `{file}:{line}` - `{import}` imported but unused
**Fix**: `ruff check . --select F401 --fix` (Python) or `goimports -w .` (Go)
### Stale TODOs ({N} instances, >90 days old)
**Impact**: High | **Effort**: Low
- `{file}:{line}` - TODO from {date} ({N} days old)
```
{context: 3 lines around the TODO}
```
**Suggestion**: {specific action}
### Dead Code ({N} instances)
**Impact**: Medium | **Effort**: Low
- `{file}:{line}` - unused function `{name}` ({confidence}% confidence)
---
## Important
### High Complexity Functions ({N} functions)
**Impact**: High | **Effort**: High
**Critical (Complexity > 20)**:
- `{file}:{line}` - `{function}()` - Complexity: {N}, Lines: {N}
**Suggestion**: Split into `{func1}()`, `{func2}()`, `{func3}()`
**Moderate (Complexity 11-20)**:
- `{file}:{line}` - `{function}()` - Complexity: {N}, Lines: {N}
### Deprecated Functions ({N} instances)
**Impact**: High | **Effort**: Medium
- `{file}:{line}` - `{old_func}()` deprecated since {version}
**Fix**: Use `{new_func}()` instead
### Duplicate Code ({N} instances)
**Impact**: High | **Effort**: High
- `{file1}:{func1}()` ({N} lines) vs `{file2}:{func2}()` ({N} lines)
**Similarity**: {N}%
**Suggestion**: Extract common logic into `{shared_func}()`
---
## Polish
### Missing Type Hints ({N} functions)
**Impact**: Medium | **Effort**: Medium
- `{file}:{line}` - `{function}({params})` - Missing {param/return} types
### Missing Docstrings ({N} functions/classes)
**Impact**: Medium | **Effort**: Medium
- `{file}:{line}` - `{function}()` public function
- `{file}:{line}` - `{class}` public class
### Naming Inconsistencies ({N} violations)
**Impact**: Low | **Effort**: Medium
- `{file}:{line}` - `{current_name}` should be `{correct_name}`
### Magic Numbers ({N} instances)
**Impact**: Low | **Effort**: Low
- `{file}:{line}` - `{value}` should be `{CONSTANT_NAME} = {value}`
---
## Files by Issue Count
| File | Issues | Types |
|------|--------|-------|
| `{file}` | {N} | {types} |
---
## Auto-Fix Commands
**Safe to run** (no logic changes):
```bash
# Python
ruff check . --select F401,F811,I001 --fix
ruff format .
# Go
goimports -w .
gofmt -w .
go mod tidy
```
---
**Next action**: Run auto-fix commands, then re-scan to verify improvements.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |