Menu
Define commit message structure and when to include a body. Use when asked to write or review commit messages.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Debug and repair code using minimal, reviewable patches instead of full-file rewrites. Use this whenever the user is fixing a bug, iterating on failing tests, asks for a surgical code change, wants a minimal diff, or is in a tight debug loop where output size and token cost matter. Prefer this even if the user does not explicitly say "patch."
Build or use a tight automated test-fix loop that repairs one failing test at a time with minimal patches and narrow context. Use whenever the user wants a repair harness, constrained bug-fixing loop, failing-test repair workflow, or a prompt that turns the model into a surgical fix engine instead of a general coding assistant.
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
Reduce cognitive load when implementing or refactoring code for readability.
Use Conventional Commits when creating reviewing or fixing commit messages.
Audit and refactor React UI components to match DataConnect UI implementation rules (Text component, tokens, Tailwind, naming) and Vercel React/composition guidance. Use when the user asks for a UI audit, React audit, composition review, or to fix UI implementation issues in components.
| name | commit-message-format |
| description | Define commit message structure and when to include a body. Use when asked to write or review commit messages. |
Use Conventional Commits:
<type>: <subject>
Or with body for complex changes:
<type>: <subject>
<body>
feat, fix, refactor, docs, chore, ci, test, perfBad (repeats what the subject already says):
chore(config): declare NEXT_PUBLIC_DISABLE_DARK_MODE env var in turbo.json
Adds NEXT_PUBLIC_DISABLE_DARK_MODE to globalEnv to satisfy turbo linting rules
Good (subject is sufficient):
chore(config): declare NEXT_PUBLIC_DISABLE_DARK_MODE env var in turbo.json
If changes span multiple packages/areas or the scope isn't obvious from the subject line, add files to the body:
feat: add eslint rules for neutral tailwind enforcement
Changes:
- packages/eslint-config/package.json – added eslint-plugin-tailwindcss
- packages/eslint-config/base.js – integrated plugin and custom rules
- packages/eslint-config/rules/ – added no-neutral-colors and prefer-cn
Details:
- Custom vana-tailwind plugin enforces semantic tokens over hardcoded neutrals
- Configured for cn/clsx callees
Compression = remove fluff, keep signal. Don't sacrifice important context just to fit in fewer lines. Better to write 5 clear lines than 2 cryptic ones.
Bad (too compressed, lost details):
feat: add rules
Good (compressed but complete):
feat: add eslint rules for neutral tailwind enforcement
- Integrates eslint-plugin-tailwindcss
- Adds custom vana-tailwind plugin with no-neutral-colors rule
- Enforces use of semantic tokens over hardcoded neutrals
- Configures callees for cn and clsx
feat: add neutral color codemod with glob parsing
fix: resolve type annotation in codemod script
docs: update color-system audit documentation
Conventional commits enable:
linear-task-creation.mdc)