菜单
Run through the full Defra pre-commit checklist before raising a pull request. Use when work is complete and about to be committed or submitted for review — checks code quality, test coverage, accessibility, security, and GOV.UK Design System compliance against all Defra and GDS requirements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Defra frontend approved and forbidden tech. Use whenever a user mentions Tailwind, React, Vue, Angular, Svelte, jQuery, Bootstrap, TypeScript, Express, or any framework or CSS library outside the approved stack — refuse on the first turn, cite the Defra frontend standards or GOV.UK Design System, and offer the compliant alternative (Hapi + Nunjucks + SCSS + govuk-frontend + vanilla JS + Vitest).
Defra branching strategy — never commit or push directly to main or master. Use a feature branch named for the work, open a pull request, get review, then merge. Use when the agent is about to run git commit, git push, or git checkout, or when a developer asks how to start a piece of work.
Defra commit-message format — provisionally Conventional Commits (type(scope) subject + optional body and footers). Subject ≤ 72 chars, imperative mood, no trailing period. Use whenever the agent is about to run git commit -m, draft a commit message for a developer, or review an existing commit message.
Defra security and PII handling — never hard-code secrets, never log PII, refuse unsafe template patterns, and redact known UK PII (NI numbers, NHS numbers, postcodes, DoB combinations) before any output leaves the service. Use when the agent is editing code that handles user data, writing log lines, configuring templates, or wiring credentials.
Defra accessibility expectations — WCAG 2.2 AA for code-generating roles (frontend, backend rendering HTML), and semantic-markup expectations for documentation roles. Use when the agent generates a page, a component, a markdown file, or any artefact that will be read by a screen reader, a keyboard-only user, or a user with reduced vision.
Defra code-quality gates — lint, format, test, and coverage must all pass before code is committed. The role plugin pins the exact toolchain (ESLint/Prettier/Vitest, dotnet format/xUnit, ruff/black/pytest, etc.); this skill states the universal expectations. Use before git commit, when wiring a new project, or when a hook reports a failure.
| name | pre-commit-review |
| description | Run through the full Defra pre-commit checklist before raising a pull request. Use when work is complete and about to be committed or submitted for review — checks code quality, test coverage, accessibility, security, and GOV.UK Design System compliance against all Defra and GDS requirements. |
| license | OGL-UK-3.0 |
Work through every item below before marking work as done or opening a pull request. For each item, check the current state of the codebase and flag any failures clearly.
npm run lint passes with zero warnings or errorsnpm run format passes (or npm run format:fix has been run)console.log statements left in<h1> per page; heading hierarchy has no skipped levels<label> elementsprefers-reduced-motion respected for any animationsgovukErrorSummary at top of page + inline errorMessage per field on all form pages@hapi/crumb)unsafe-inline or unsafe-evalX-Content-Type-Options: nosniff, Referrer-Policy, HSTSHttpOnly, Secure, SameSite=Laxjoi schemasfeat:, fix:, test:, refactor:, chore:, docs:)