tidylisted

## Pre-computed context Current branch: !`git branch --show-current 2>/dev/null || echo "unknown"` Recent commits: !`git log --oneline -5 2>/dev/null || echo "no commits"` Working tree status (empty = clean): !`{ git status --porcelain 2>/dev/null || echo "(git status unavailable)"; } | head -20` Open chore/tidy-* PRs: !`${CLAUDE_SKILL_DIR}/scripts/open-pr-count.sh 2>/dev/null | { grep -E '^(Open tidy|Throttle)' || echo "unknown"; }; :` ## Variables Arguments: `$ARGUMENTS` ## Purpose Tidy is the proactive "Boy Scout in passing" loop. Step zero of the long-game improvement story. Answers: "What small structural improvements can I safely make to one slice of the codebase today, and ship as one tight PR, without mixing structural and behavioral changes?" This skill encapsulates the agentic application of three converging ideas: - **Kent Beck, *Tidy First?* (2024)**. Small, named refactorings called "tidyings" (Beck's 15), separated from behavioral changes by commit and by PR. *"Always one or the other, never both at the same time."* - **Robert C. Martin / Steve Smith, Boy Scout Rule**, leave the campsite cleaner than you found it. Empirically validated against the *Pragmatic Programmer*'s Broken Windows hypothesis: small drift compounds. - **Adam Tornhill / CodeScene 2026, agentic refactoring research**, autonomous AI agents introduce defects ~30% more often in unhealthy code. Agents need a higher Code Health bar than humans. Structure-only Boy Scout work is the safest ag