codebase-taskslisted

# Codebase Task Finder Scan the codebase for work that should be done — TODOs, fixmes, tech debt, dead code, missing error handling at boundaries, and low-hanging improvements. Prioritize by impact and effort, and optionally fix the quick wins. **Input:** "$ARGUMENTS" ## Workflow ### 1. Determine Scope - If a path or scope is provided (e.g., `apps/sync`, `packages/`, `src/`), limit the scan to that area - If no scope is provided, scan the full repo but focus on `src/`, `apps/`, `packages/`, `lib/` — skip `node_modules`, `dist`, `.next`, vendor directories ### 2. Scan for Explicit Markers Search for developer-left markers: ```bash # TODOs and FIXMEs grep -rn "TODO\|FIXME\|HACK\|XXX\|TEMP\|WORKAROUND" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.go" --include="*.py" <scope> # Disabled or skipped tests grep -rn "\.skip\|xdescribe\|xit\|@skip\|@disabled" --include="*.test.*" --include="*_test.*" <scope> # Commented-out code blocks (3+ consecutive commented lines) ``` ### 3. Scan for Implicit Issues Read key files and look for: **Dead code:** - Exported functions/types that are never imported elsewhere - Unused variables flagged by linter configs but not yet cleaned up - Files that haven't been modified in 6+ months and aren't referenced **Error handling gaps:** - Empty catch blocks - Caught errors that are silently swallowed (no log, no rethrow) - API endpoints without try/catch at the handler level **Consistency issues:** - Mixed patterns in th