Matt Pocock 杂项 - setup-pre-commit

Model: qwen-max | ¥0.15/call

工程方法论GPT-4.1工程实践setuppre

setup-pre-commit：mattpocock/skills 方法论: misc/setup-pre-commit，适用于工程实践、代码质量与开发流程优化。

Calls: 1

Skill Documentation

Matt Pocock 杂项 - setup-pre-commit

摘要

setup-pre-commit：mattpocock/skills 方法论: misc/setup-pre-commit，适用于工程实践、代码质量与开发流程优化。

> 来源: mattpocock/skills (141k stars) — Total TypeScript 创始人 Matt Pocock

> 类目: 杂项

> 原文件: skills/misc/setup-pre-commit/SKILL.md

> 模型推荐: gpt-4.1 (代码工程)

这个 skill 是干嘛的

Matt Pocock (Total TypeScript, 141k stars) 沉淀下来的"日常代码工程动作"skill 模板。

每一个对应一个具体动作(代码评审 / TDD / 重构 / 文档对齐 / 任务交接),不是工具,是"该怎么干这件事"的工作流模板。

michael 强调"skill 要有相应的指导功能,指导用户使用",所以这里加了下面两节让 Agent 和用户对接。

---

🤖 Agent 使用说明

1. 接到任务后先按这个 skill 的检查清单走一遍

2. 清单里如果出现"先做 X 才能做 Y"的红线 → 必须先完成 X

3. 跑完清单后开始动手(改代码 / 写文档 / 评审)

4. 完工前用 `verification-before-completion`(superpowers) 或 `verification` 类 step 自检

5. 任务量大时考虑用 `dispatching-parallel-agents`(superpowers) 或 `wayfinder`(mattpocock) 拆解

👤 用户需要做什么?

1. 告诉 Agent 你要做什么(一句话即可)

2. Agent 跑 skill 清单时不要打断 — 它可能在收集上下文

3. 如果 Agent 主动问你"代码评审要不要安排一个 reviewer"等决策点 → 直接回答

4. 完工后让 Agent 跑一遍自检再交回

5. 整个过程 Agent 自动化,不需要手工介入

---

原 skill 内容(mattpocock/skills/misc/setup-pre-commit/SKILL.md)

---

name: setup-pre-commit

description: Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

---

Setup Pre-Commit Hooks

What This Sets Up

**Husky** pre-commit hook
**lint-staged** running Prettier on all staged files
**Prettier** config (if missing)
**typecheck** and **test** scripts in the pre-commit hook

Steps

1. Detect package manager

Check for `package-lock.json` (npm), `pnpm-lock.yaml` (pnpm), `yarn.lock` (yarn), `bun.lockb` (bun). Use whichever is present. Default to npm if unclear.

2. Install dependencies

Install as devDependencies:

husky lint-staged prettier

3. Initialize Husky

npx husky init

This creates `.husky/` dir and adds `prepare: "husky"` to package.json.

4. Create `.husky/pre-commit`

Write this file (no shebang needed for Husky v9+):

npx lint-staged
npm run typecheck
npm run test

**Adapt**: Replace `npm` with detected package manager. If repo has no `typecheck` or `test` script in package.json, omit those lines and tell the user.

5. Create `.lintstagedrc`

{
  "*": "prettier --ignore-unknown --write"
}

6. Create `.prettierrc` (if missing)

Only create if no Prettier config exists. Use these defaults:

{
  "useTabs": false,
  "tabWidth": 2,
  "printWidth": 80,
  "singleQuote": false,
  "trailingComma": "es5",
  "semi": true,
  "arrowParens": "always"
}

7. Verify

[ ] `.husky/pre-commit` exists and is executable
[ ] `.lintstagedrc` exists
[ ] `prepare` script in package.json is `"husky"`
[ ] `prettier` config exists
[ ] Run `npx lint-staged` to verify it works

8. Commit

Stage all changed/created files and commit with message: `Add pre-commit hooks (husky + lint-staged + prettier)`

This will run through the new pre-commit hooks — a good smoke test that everything works.

Notes

Husky v9+ doesn't need shebangs in hook files
`prettier --ignore-unknown` skips files Prettier can't parse (images, etc.)
The pre-commit runs lint-staged first (fast, staged-only), then full typecheck and tests

常见问题（FAQ）

使用「setup-pre-comm」这个 skill 能解决什么问题?

本 skill 专注于setup-pre-comm，mattpocock/skills 方法论: misc/setup-pre-commit。它将相关流程标准化，帮助用户更快拿到可靠结果，减少重复手工操作。

什么情况下适合使用「setup-pre-comm」?

当你需要在setup-pre-commit相关工作中获得稳定、可复用的产出时最适合——无论是单次任务还是纳入日常工作流，都能直接调用。

使用「setup-pre-comm」前需要准备什么?

需要一个具体的项目或任务上下文，最好带有代码仓库或需求文档。

FAQ