القائمة
Enforce clean, spec-compliant commit messages and commit hygiene. Use when writing, reviewing, or correcting commit messages, deciding commit scope, or preparing a commit for merge.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | commit-discipline |
| description | Enforce clean, spec-compliant commit messages and commit hygiene. Use when writing, reviewing, or correcting commit messages, deciding commit scope, or preparing a commit for merge. |
Use Conventional Commits 1.0.0 with minimal noise and maximum signal.
.agents/skills/conventional-commits/SKILL.md first.<type>[optional scope][optional !]: <description>
[optional body]
[optional footer(s)]
type.add, fix, refactor, remove, rename).feat: user-facing featurefix: user-facing bug fixdocs: documentation onlyrefactor: no user-visible behavior changeperf: performance improvementtest: tests onlybuild: build tooling/dependenciesci: CI/CD pipeline/workflowchore: maintenance not covered aboverevert: reverts a previous commitPrefer feat or fix when either is true.
fix(connect): ....Use one of these patterns:
type(scope)!: descriptionBREAKING CHANGE: <details>BREAKING CHANGE footer token must be uppercase.
Include a body only when it adds non-obvious context:
Do not restate the diff.
Use footers for structured metadata:
BREAKING CHANGE: ...Refs: #123Reviewed-by: NameCo-authored-by: Name <email>update stuff, fix things).When asked to improve a message:
fix(connect): preserve return path after auth handoff
feat(auth)!: require signed nonce for session creation
BREAKING CHANGE: unsigned nonce requests are now rejected by default.
refactor(login): isolate callback parsing from page state updates
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.