continuous-improvementlisted

# Continuous Improvement Audit a codebase, find real improvements, implement the best ones as PRs, self-review, and assess merge safety. This is a journey skill — it orchestrates a full workflow from audit to PR-ready. **Input:** "$ARGUMENTS" ## Before Starting 1. Read the repo's `CLAUDE.md` for conventions (commit format, branch naming, style rules) 2. Read this skill's `feedback.md` if it exists — apply all rules from prior feedback before proceeding 3. Check git status — must be on a clean working tree. If there are uncommitted changes, stop and tell the user. ## Phase 1: AUDIT Scan the codebase for improvements. Use the same methodology as the `codebase-tasks` skill: **Scope:** If a path is provided, scan that area. If `--focus` is set, narrow to that category. Otherwise scan the full repo. **Categories to scan:** | Category | What to Look For | |---|---| | **Security** | Empty catch blocks hiding errors, SQL/injection risks, auth gaps, hardcoded secrets, missing input validation at boundaries | | **Performance** | N+1 queries, unnecessary re-renders, missing indexes hinted at by query patterns, synchronous I/O in hot paths | | **Tech debt** | TODOs/FIXMEs older than 3 months, commented-out code, dead exports, duplicated logic, mixed patterns in same directory | | **Dependencies** | Major version bumps available, deprecated packages, unused dependencies | | **Tests** | Skipped tests, missing error path coverage, test files that import modules that no longer exist