القائمة
Commits staged changes to the repository with conventional commit format. Use when the user wants to create a git commit, finalize work, or save changes with a structured commit message.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | commit |
| description | Commits staged changes to the repository with conventional commit format. Use when the user wants to create a git commit, finalize work, or save changes with a structured commit message. |
| context | fork |
| allowed-tools | Bash(git status),Bash(git add),Bash(git commit),Bash(git branch),AskUserQuestion |
Commit changes to the repository using git.
git statusgit add <file1> <file2> ... or git add .git branch --show-current[A-Z]+-\d+ (e.g., PRTIMES-123, JIRA-456)AskUserQuestiongit commit -m "<commit message>"<type>: <description> [ISSUE-NUMBER]
<WHY - reason/background for the change>
| Type | Usage |
|---|---|
feat | Add new feature |
fix | Bug fix |
refactor | Refactoring (no functional change) |
test | Add or modify tests |
docs | Documentation changes |
style | Code style changes (formatting, etc.) |
chore | Build or configuration changes |
perf | Performance improvements |
[ISSUE-NUMBER] formatfeat: Add user authentication feature [PRTIMES-123]
Introduced JWT-based authentication mechanism to meet security requirements.
Changed from session management to token-based as existing approach did not meet requirements.
fix: Fix validation error on login screen [JIRA-456]
Resolved issue where 500 error occurred when empty string was submitted.
Added server-side validation as frontend validation was insufficient.
Runs difit to launch a browser-based diff review UI and reports the result. Use when the user wants to review diffs with difit, visually review code changes in a browser, or says "difit でレビュー".
Orchestrates a structured TDD development workflow including codebase exploration, work planning (with test plan), implementation, quality checks (tests/lint/format), and CodeRabbit code review. Triggers when the user wants to implement a feature, fix a bug, refactor code, or requests TDD-based development. Also triggers on keywords like "develop", "implement", "build", "code this".
Helps improve the tdd-development skill. Triggers on keywords like "tdd skill improvement", "modify tdd-development", "fix phase N", or "improve tdd workflow".
Runs project quality checks (tests, lint, static analysis, formatting) and reports results. Use after code changes to validate quality, or when the user asks to run tests, lint, or static analysis.
Performs code review using CodeRabbit CLI and provides actionable feedback. Use when the user requests a CodeRabbit review, wants automated code analysis, or needs pre-merge quality checks.
Fetches unresolved review comments from the GitHub PR for the current branch. Use when checking PR comments, addressing reviewer feedback, fixing review issues, or responding to code review.