cdkd: Skill for Claude Code

Local Quality Check

Run all local quality checks. Use during development to verify the current state quickly.

First: self-review on four axes

Walk these BEFORE the commands below and before committing. A green suite says the tests pass, not that the work is good, and none of these four is something a runner reports.

1. Implementation gaps — the parallel change forgotten in a sibling command; a test or a doc not added.
2. Oddities — dead code, leftover names, a half-applied refactor.
3. Polish opportunities — small in-scope improvements; default to including them when they touch the same files and carry no behavior-break risk.
4. Regression risk — the full suite, and the call sites of anything renamed or removed.

Say out loud what you found, then fix it before running the checks.

Steps

Run these sequentially and report results.

1. Worktree pre-flight: [ -d node_modules ] || vp install --frozen-lockfile. git worktree add does not copy node_modules, and without it vp check fails with an unnamed typescript(tsconfig-error): Invalid tsconfig — Cannot find type definition file for 'node', reading like a broken fixture tsconfig.

2. vp check --fix (typecheck + lint + Prettier, auto-fix), then vp run check — the exact command CI's check-build-test job runs. They are NOT equivalent: vp check --fix has passed with 0 errors on a tree vp run check failed. Do not substitute vp run lint:fix, which does not touch Prettier, so a lint:fix-only run passes locally while CI fails Formatting issues found. Run both; CI parity comes from the second.

3. vp run typecheck:test — type-checks tsconfig.test.json (tests/**). vp check only type-checks tsconfig.json (src + types), which excludes **/*.test.ts, and vp test's Type Errors line covers only *.test-d.ts. A wrong import type or stale mock shape in a test file is invisible without this step.

4. vp run build.