メニュー
Prepare a compartment repo commit that matches commitlint type and scope rules and runs through Husky validation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.
Handle export, entrypoint, scaffolding, or deletion changes that can create dead runtime surface or Knip runtime drift in the compartment repo.
Run or delegate a browser-first smoke test of the local compartment through browser-use as a real user: boot or reuse the local stack, install or log in, deploy the repo smoke fixtures, verify CLI status/logs, and exercise protected app login/logout flows.
Implement repo changes by starting with a required preflight subagent, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.
Open or reuse a repo PR, then monitor checks, merge readiness, and review feedback until the PR is done, blocked, or redirected.
Run a required subagent preflight before implementation and return a short coding brief: where to edit, what to avoid, what lint or runtime traps matter, and what to validate.
| name | commit-a-change |
| description | Prepare a compartment repo commit that matches commitlint type and scope rules and runs through Husky validation. |
Use this skill when the user asks to commit work in the compartment repo.
commitlint.config.cjs.husky/pre-commit.husky/commit-msgtype values are in type-enum; allowed scope values are in scope-enum.type(scope): subject, with a header no longer than 100 characters.git commit, .husky/pre-commit starts pnpm lint-staged, pnpm check, and pnpm check:duplicates, so manual validation before commit should stay limited to the checks that matter for the current diff.git commit -m ...; if Husky blocks the commit, fix the failure and retry with a new non-interactive commit.--no-verify.