Set up checks that run before each commit using Husky, lint-staged, and Prettier. Format staged files, run existing type-check and test scripts, then verify and commit the configuration.
在当前仓库设置 Husky pre-commit hooks，集成 lint-staged (Prettier)、类型检查和测试。适用于用户想添加 pre-commit hooks、设置 Husky、配置 lint-staged，或在提交时运行格式化、类型检查和测试时。
Review the instructions the agent will receive before you install.
检查 package-lock.json (npm)、pnpm-lock.yaml (pnpm)、yarn.lock (yarn)、bun.lockb (bun)。使用存在的那个。不清楚时默认 npm。
作为 devDependencies 安装：
husky lint-staged prettier
npx husky init
这会创建 .husky/ dir，并向 package.json 添加 prepare: "husky"。
.husky/pre-commit写入这个文件（Husky v9+ 不需要 shebang）：
npx lint-staged
npm run typecheck
npm run test
Adapt：把 npm 替换为检测到的 package manager。如果 repo 的 package.json 没有 typecheck 或 test script，就省略对应行并告知用户。
.lintstagedrc{
"*": "prettier --ignore-unknown --write"
}
.prettierrc（如果缺失）只有没有 Prettier config 时才创建。使用这些 defaults：
{
"useTabs": false,
"tabWidth": 2,
"printWidth": 80,
"singleQuote": false,
"trailingComma": "es5",
"semi": true,
"arrowParens": "always"
}
.husky/pre-commit 存在且可执行.lintstagedrc 存在prepare script 是 "husky"npx lint-staged 验证可用Stage 所有 changed/created files，并用 message 提交：Add pre-commit hooks (husky + lint-staged + prettier)
这会经过新的 pre-commit hooks，是一个不错的 smoke test。
prettier --ignore-unknown 会跳过 Prettier 无法 parse 的 files（images 等）No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.