Menu
Run format, typecheck, test, and lint across the monorepo. Use after implementing changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | verify |
| description | Run format, typecheck, test, and lint across the monorepo. Use after implementing changes. |
Delegate to the verify subagent to run the full verification pipeline (rebase, format, typecheck, test, lint) and fix any issues it finds when the runtime supports delegated helpers. The subagent runs on Sonnet, which is cheaper than the main session and well-suited to the mechanical run-parse-fix loop.
If runtime policy forbids delegated helpers/subagents unless the user explicitly requested them, treat delegation as unavailable and use the direct-command fallback below. Do not stop at a partial check just because delegation is unavailable.
Invoke the verify subagent in a single call when available. Wait for it to complete and surface the result.
Do NOT run the verification commands yourself in the main session when the helper is available — that defeats the cost saving. The subagent's prompt already contains the full procedure (see .claude/agents/verify.md).
Use this only when the runtime does not permit delegated helpers/subagents. Run the full pipeline directly from the repository root and report the exact commands and results:
# Fresh worktrees share .git/ but not apps/node_modules.
if [ ! -d apps/node_modules ]; then
(cd apps && pnpm install --frozen-lockfile)
fi
# If the branch is behind main, rebase first.
git fetch origin main
git merge-base --is-ancestor origin/main HEAD || echo "branch is behind origin/main"
git rebase origin/main
# make typecheck uses the top-level Makefile path and can bypass package
# pretypecheck hooks, so generate web metadata before typecheck.
make fmt
node apps/web/scripts/generate-release-notes.mjs
node apps/web/scripts/generate-changelog.mjs
make typecheck
make test
make lint
Before rebasing, check whether origin/main is already an ancestor of HEAD.
If tracked files for the intended change are dirty, stash only those pathspecs
before git rebase origin/main, then pop the stash before running
make fmt/typecheck/test/lint. Do not use a broad git stash that could hide
unrelated user changes. If you miss this and git rebase origin/main fails
because of unstaged tracked changes, apply the same pathspec-only stash flow,
then rerun the rebase. Resolve conflicts before continuing verification.
If make fmt changes files, review the diff and continue with the remaining commands. If any command fails, fix the issue and re-run the failed command; for formatter-caused changes, re-run any affected checks before reporting success.
If make typecheck still fails because apps/web/generated/changelog.json or
apps/web/generated/release-notes.json is missing, regenerate them and rerun
make typecheck:
(cd apps/web && node scripts/generate-release-notes.mjs)
(cd apps/web && node scripts/generate-changelog.mjs)
When verifying the web package directly, prefer:
(cd apps/web && pnpm run typecheck)
That package script runs pretypecheck and regenerates
generated/changelog.json / generated/release-notes.json. If troubleshooting
the web package directly, prefer the package-local script over workspace-filter
forms so TypeScript runs in the intended package context.
If the aggregate make lint wrapper stalls or does not provide useful progress, run the backend and frontend lint checks directly instead and record the substitution in your result:
make lint-backend
cd apps && pnpm --filter @kandev/web lint
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.