clean-code-quick-scan-commands
Sub-skill of clean-code: Quick Scan Commands.
Best use case
clean-code-quick-scan-commands is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of clean-code: Quick Scan Commands.
Teams using clean-code-quick-scan-commands should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/quick-scan-commands/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clean-code-quick-scan-commands Compares
| Feature / Agent | clean-code-quick-scan-commands | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of clean-code: Quick Scan Commands.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Quick Scan Commands
## Quick Scan Commands
Run these before reviewing or merging code:
```bash
# Find files exceeding 400-line hard limit
find src/ -name "*.py" -exec wc -l {} + | awk '$1 > 400 {print $1, $2}' | sort -rn | head -20
# Find functions exceeding 50 lines (approximate — counts def blocks)
grep -n "^ def \|^def " src/**/*.py | awk -F: '{print $1, $2}' | head -30
# Oversized files by severity
echo "=== CRITICAL (>1000 lines) ===" && find src/ -name "*.py" -exec wc -l {} + | awk '$1>1000{print}' | sort -rn
echo "=== HIGH (400-1000 lines) ===" && find src/ -name "*.py" -exec wc -l {} + | awk '$1>400 && $1<=1000{print}' | sort -rn
# Dead code: files named *_unused.py or *_old.py
find src/ \( -name "*_unused.py" -o -name "*_old.py" -o -name "*_bak.py" \) | head -20
# Duplicate class names (possible God Object fragmentation)
grep -r "^class " src/ | sed 's/.*class //' | sed 's/[:(].*//' | sort | uniq -d
```
---Related Skills
mnt-analysis-cleanup
Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
git-worktree-cleanup-at-scale
Identify and remove stale git worktrees blocking branch deletion in multi-repo environments
git-worktree-cleanup-and-branch-reconciliation
Systematic process for cleaning up stale git worktrees, resolving merge conflicts in diverged branches, and reconciling branch state across multiple repositories.
git-worktree-cleanup-and-branch-hygiene
Systematic approach to cleaning up stale git worktrees, orphan branches, and branch hygiene at scale across multiple repos
git-blob-size-filter-cleanup
Strip oversized blobs from unpushed commits using git filter-branch when GitHub's 100 MB limit blocks push
clean-worktree-integration-from-dirty-main
Land validated issue work from isolated worktrees when the main checkout is dirty by creating a fresh integration worktree, cherry-picking only implementation commits, re-running combined validation, and preparing push/closeout artifacts.
clean-code
Clean code enforcement for workspace-hub Python repos: file/function size limits, God Object detection, naming rules, dead code removal, and refactor decision guidance. Consult before writing new modules or accepting large files.
skill-dedup-collision-reconciliation-with-content-security-scan
Reconcile duplicate/colliding workspace-hub skills without losing useful content, while avoiding pre-commit skill-content security scan regressions.
live-writer-branch-cleanup-guard
Guardrails for multi-repo sync and branch cleanup when workspace-hub or another shared repo has active writer sessions, worktree-backed branches, or unrelated-history branches.
full-branch-cleanup-and-worktree-hygiene
Track all dirty/untracked workspace-hub changes, merge stale branches into main, clean remote/local branches, and remove stale worktrees while preserving tracked nested gitlinks.
blocked-branch-preserve-tag-cleanup
Safely clean stale local branches that cannot be merged by preserving them with local tags before deletion