القائمة
Generate conventional commit with staged changes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose and fix a failing SonarQube quality gate on the current branch's merge request — resolves the project + PR, reads the failing conditions, then fixes new violations and coverage gaps. Use when the user says "fix the sonarqube gate", "the sonar quality gate is failing", or after a pipeline reports a red SonarQube check.
Review a merge request for security, performance, architecture, style, and improvements
Research a task and write a phased plan to .plan/<slug>.md without implementing it. Use when the user wants to plan a feature or change before building, asks to "make a plan", or when a task is large enough to design before touching code. Replaces built-in plan mode.
Explore several design solutions for a task and compare their trade-offs without implementing anything. Use when the user wants to weigh approaches before committing, asks to "explore options", "compare designs", or "what are my options" for a change.
Implement a piece of work based on a spec or set of tickets.
Create unpublished inline DRAFT review comments on a GitLab merge request diff via the GitLab API. Use when a code review has produced findings that should be attached to exact diff lines as drafts (not published) so the human can review and submit them in one batch. Carries a ready-to-post dataset for Phoenix MR !145 (View360 view-based rework).
| description | Generate conventional commit with staged changes |
| name | conventional-commit |
| model | sonnet |
| disable-model-invocation | true |
You are committing staged changes in the current git repository. Follow these rules exactly.
Run these commands to understand the current state:
git status --porcelaingit diff --cached --name-onlygit diff --cachedgit log --oneline -5NEVER include any of the following in the commit message, body, footer, or trailers:
Co-Authored-By trailers mentioning Claude, Anthropic, or any AISigned-off-by, Generated-by, or similar trailers referencing AIViolating this rule makes the commit invalid. Double-check before executing.
If git commit fails because a pre-commit hook rejected it (lint, knip, type-check, prettier, tests, etc.):
knip: off/@knip/ignore comments, no deleting exports, no --fix, no touching unrelated files.git add is still forbidden).Fixing hook failures is the user's call, not yours. Your job is only to compose the message and commit what is already staged.
git diff --cached) to understand what was modifiedgit add. Only commit what the user has already staged.git commit with the generated message — no Co-Authored-By or AI trailersSee how a minor change to your commit message style can make a difference.
git commit -m "<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
<type>(<optional scope>): <description> empty line as separator <optional body> empty line as separator <optional footer>
chore: init
Merge branch '<branch name>'
Follows default git merge message
Revert "<reverted commit subject line>"
Follows default git revert message
feat Commits that add, adjust or remove a new feature to the API or UIfix Commits that fix an API or UI bug of a preceded feat commitrefactor Commits that rewrite or restructure code without altering API or UI behavior
perf Commits are special type of refactor commits that specifically improve performancestyle Commits that address code style (e.g., white-space, formatting, missing semi-colons) and do not affect
application behaviortest Commits that add missing tests or correct existing onesdocs Commits that exclusively affect documentationbuild Commits that affect build-related components such as build tools, dependencies, project version, CI/CD
pipelines, ...ops Commits that affect operational components like infrastructure, deployment, backup, recovery procedures, ...chore Miscellaneous commits e.g. modifying .gitignore, ...claude Commits that affect .claude/The scope provides additional contextual information.
! before the : in the subject line e.g.
feat(api)!: remove status endpointThe description contains a concise description of the change.
This commit will... or This commit should....)The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain issue references and information about Breaking Changes
Closes #123, Fixes JIRA-456)BREAKING CHANGE:
BREAKING CHANGE:BREAKING CHANGE:feat or fix) incremented the minor versionfeat: add email notifications on new direct messages
feat(shopping cart): add the amazing button
feat;: remove ticket list endpoint
refers to JIRA-1337
BREAKING CHANGE: ticket endpoints no longer supports list all entities.
fix(shopping-cart): prevent order an empty shopping cart
fix(api): fix wrong calculation of request body checksum
fix: add missing parameter to service call
The error occurred due to <reasons>.
perf: decrease memory footprint for determine unique visitors by using HyperLogLog
build: update dependencies
build(release): bump version to 1.0.0
refactor: implement fibonacci number calculation as recursion
style: remove empty line