Menü
Generates a Git commit message based on staged, modified, or untracked changes
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.
Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).
Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.
Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions
| name | commit |
| description | Generates a Git commit message based on staged, modified, or untracked changes |
As an expert in writing Git commit messages, your task is to generate a commit message that follows the Conventional Commits specification and the commitizen convention.
question tool for EVERY user interaction — never ask questions as plain texttype(scope): brief description
- detailed description point 1
- detailed description point 2 (if needed)
- detailed description point 3 (if needed)
Check for staged changes.
git diff --staged --quiet --exit-code.git diff --staged.Check for modified and untracked files.
git status --porcelain.No changes to commit.Handle untracked files.
git status --porcelain for files prefixed with ??.question tool with: question="There are untracked files. Do you want to include them in the commit message generation?", header="Untracked files", options=[{label="Yes, include them", description="Include untracked files in the commit message analysis"}, {label="No, skip them", description="Only analyze modified/staged files"}]git diff and git ls-files --others --exclude-standard.git diff.git diff.Adhere to Commitizen Conventions.
feat, fix, docs, style, refactor, perf, test, choreConfirm the commit message.
question tool with: question="Does this commit message look good?", header="Confirm message", options=[{label="Yes, looks good", description="Proceed to commit"}, {label="No, let me give feedback", description="Provide feedback to improve the message"}]Iterate on the commit message.
question tool to ask for feedback: question="What changes would you like to make to the commit message?", header="Refine message", options=[{label="Custom feedback", description="Type your specific feedback or requested changes"}]Confirm the commit.
question tool with: question="Do you want to commit these changes?", header="Execute commit", options=[{label="Yes, commit", description="Run git commit with the generated message"}, {label="No, cancel", description="Abort the commit workflow"}]git commit -m "{{generated_commit_message}}".feat(auth): add OAuth2 integration
- implement Google OAuth provider
- update user authentication flow
- add integration tests
fix(api): resolve data validation issues
- fix null pointer exceptions in user data
- improve input validation for API endpoints