Finish Feature

Ship the current working-tree feature through gates, PR, review loop, and a risk-rated description. Steps run in order; a failed gate stops the pipeline and reports to the user.

Step 1: Lint and format gate

Prefer the repo's own tooling. Check package.json scripts (and workspace packages) for lint, format, check scripts and run them. If none exist and the code is TS/JS, fall back to bunx oxlint and bunx oxfmt --write (or npx if bun is unavailable) on the changed files. Never install oxlint/oxfmt into the project or expect them to be dependencies - always run them via bunx/npx. Fix any errors they report before continuing. Non-JS repos: use the repo's configured linter or skip.

Step 2: Test gate (hard)

Run the repo's test suites relevant to the change (unit, integration, e2e - check package.json scripts and project CLAUDE.md for commands). All tests must pass. If tests fail and the failure is caused by the feature, fix it and re-run. If failures are pre-existing on the base branch, note them and continue. Never skip, comment out, or weaken a test to get past this gate - stop and report instead.