Claude Skills · Code Review & Testing
Factory Verification Engineer
nonlinear-xyz/factory-kitUse to design the verification strategy for a change — what would prove it correct, given its blast radius, and what is currently unverifiable. Read-only — outputs a verification plan and a gap list, not a review and not code. Sister to `code-reviewer` (which finds defects in a diff) and the generalization of `db-migration-engineer`'s verify-stage discipline to all changes. Carries the four-tier eval spectrum and the score model from `factory-verification.md`. Invoke before merging a nontrivial change, when onboarding a risky area, or when asking "how would we know this is right?
At a glance
This skill is for Code Review & Testing and helps you design a verification strategy for a change, identify gaps in test coverage, and assess blast radius and risk.
/plugin marketplace add nonlinear-xyz/factory-kit
/plugin install factory-verification-engineer
Setup, runtime and requirements describe nonlinear-xyz/factory-kit, the repo this skill ships in.
Testing StrategyChange VerificationRisk AssessmentTest Coverageblast-radius
Also in nonlinear-xyz/factory-kit
View the repoMotion discipline distilled across builds. Attention as a fixed per-viewport budget, figure/ground separation (calm the ground, load motion...
API conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router co...
Use when designing or implementing API endpoints — server actions, tRPC procedures, REST routes for external consumers. Carries the factory'...
Auth and authorization conventions distilled across builds with three different auth stacks (Better Auth + orgs, Supabase Auth + RLS, Clerk)...
Use when wiring auth into a new project, switching auth providers, or adding role/org features. Carries the factory's auth conventions — the...
CI and pull-request review conventions. One canonical `.github/workflows/ci.yml` is the merge gate (typecheck, lint, test, build, claude-rev...
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree
Use to review a PR, diff, or recently-written code against the factory's conventions. Read-only — outputs structured review, not diffs. Carr...
Commit message and branch convention — Conventional Commits format with a Linear issue reference required in subject or body. Includes the c...
Database schema, ORM, and migration conventions across builds. Drizzle as default with domain-partitioned schema modules, shared `timestamps...
Use when designing or implementing data ingestion, CSV imports, time-series storage, Python services that sit alongside Next.js, simulation...
Data ingestion and pipeline conventions for projects that import CSVs, run simulations, or operate Python services alongside Next.js. Covers...
Other Code Review & Testing skills
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...
Use when you need to resolve an in-progress git merge/rebase conflict.
A relentless interview that asks every frontier question at once, round by round.