drive-codelisted

Use when the user says "drive the code", "/drive-code", "clean up the code in this PR", "make sure the touched files follow best practices", or asks Claude to do a code-quality pass on the files a PR (or working tree) touches. Evaluates each touched file for single-responsibility, modularity, service/repository pattern compliance, utility placement, naming, length, and runs the project's linter + formatter. Applies mechanical fixes automatically; proposes (with diff) any structural refactor before changing it. Does NOT verify the feature's behaviour (use /drive-feature) or its UX (use /drive-ux).
0xdeafcafe/skills · ★ 0 · Code & Development · score 75

Install: claude install-skill 0xdeafcafe/skills

# drive-code - per-file code-quality pass on every touched file drive-code looks at every file the PR changed and asks: does this file still earn its keep after this change? SRP, layering, utility placement, length, naming, linter + formatter pass. Mechanical fixes (lint --fix, format) apply automatically. Structural changes (split file, extract function, move util) show a diff first, apply, and get flagged in the report. ## Phase 0 - Scope Decide which files are in scope, in this priority order: 1. **PR context**: `gh pr diff --name-only` against the base branch. 2. **Working tree**: `git diff --name-only HEAD` for uncommitted work. 3. **An explicit list** passed by the user. Exclude: lockfiles, generated files (`linguist-generated=true`, `dist/`, `build/`, `generated/`, `__generated__/`, `*.pb.*`), binary blobs, fixtures (`fixtures/`, `__fixtures__/`, `testdata/`), vendored code (`vendor/`, `third_party/`, `external/`). ## Phase 1 - Discover the toolchain Detect linter, formatter, TS/JS symbol intel, and test runner from config files. See `references/code-checklist.md` for the detection table. Read `CLAUDE.md` and the relevant `README.md` first - the project may document conventions that override defaults. ## Phase 2 - Mechanical fixes (always safe to apply) Run in parallel where possible: ```bash <linter> --fix <paths> <formatter> --write <paths> tslsp code-action --file <path> --kind source.organizeImports --apply 0 ``` Diff what changed. Mechanical fixes are