菜单
Periodic code health checkup for design drift not caught by CI. Use at version bumps or when asked for a code health check / 健康診断 / 健診. Audits logged advisory deviations and runs a deepen-modules pass.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Perform a project release: bump the semver `version` in package.json, summarize changes since the last release, and hand off to the health-checkup. Use when cutting a release, bumping the project version, or asked to "version up".
Project coding conventions and architecture constraints. Use when implementing, creating, or modifying components and modules (e.g. "create a component", "implement this feature").
Create a PR aligned with the AI-led workflow: summary, design (when relevant), impact and risks. Use when creating a pull request, opening a PR, pushing for review, or completing implementation of an issue.
Triage GitHub PR review feedback (top-level, inline, threads); implement agreed items; escalate disagreements or questions. Includes lint/test checks, per-thread replies with commit SHA, and a chat summary. Use when fixing review feedback on an open PR—not for greenfield implementation only.
Propose codifying reusable lessons from trial-and-error or explicit user requests into lint, rules, or skills. Use near task completion after failed first attempts, or when the user asks to "make it a rule" or "leave a lesson". NOT for empirically testing instructions on fresh agents (tune-prompt) or drafting a new skill without a lesson to codify.
Empirically test skills, rules, or prompts on fresh agents with scored checklists; edit one theme per cycle until instructions land. Use after creating or heavily revising agent instructions, when agents misbehave on those instructions, or when validating that a skill is followed correctly. NOT for codifying runtime lessons after task failures (suggest-improvement) or drafting a new skill without empirical validation.
| name | health-checkup |
| description | Periodic code health checkup for design drift not caught by CI. Use at version bumps or when asked for a code health check / 健康診断 / 健診. Audits logged advisory deviations and runs a deepen-modules pass. |
Catches what CI cannot: design drift (deep modules, layering, abstractions) that accumulates silently between checkups.
| Concern | Owner |
|---|---|
| Issue intent, acceptance criteria | Human |
| Actual runtime behavior | Human |
| Mechanical quality (structure, types, format, commits) | CI — enforcement-inventory rule |
| Design health | This checkup |
The audit only works if drift left a trail: every PR logs intentional advisory deviations under Impact and risks (create-pull-request skill). An undocumented deviation is the one a checkup cannot find.
Run at each release; keep the interval small (design debt compounds).
deepen-modules skill as a structured pass over the areas changed since then.coding-guide (Tailwind tokens, Storybook coverage, tests for behavior changes).