Menü
Writes a single Conventional Commits message from a description of changes or a git diff. Use when the user asks for a commit message, or mentions committing, staging, or a diff.
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
| name | conventional-commit |
| description | Writes a single Conventional Commits message from a description of changes or a git diff. Use when the user asks for a commit message, or mentions committing, staging, or a diff. |
Output exactly one Conventional Commits message and nothing else — no backticks, no code fences, no commentary.
<type>(<optional scope>): <summary>
<optional body explaining WHY, wrapped at 72 columns>
<type>: one of feat, fix, docs, style, refactor, perf, test,
build, ci, chore, revert.! after the type/scope (or a BREAKING CHANGE: body footer) for a
breaking change.Input: Added user authentication with JWT tokens Output: feat(auth): add JWT-based login and token validation
Input: Fixed dates rendering in the wrong timezone on reports Output: fix(reports): use UTC timestamps in date formatting
Input: Upgraded deps and standardized error responses (drops Node 16) Output: chore!: upgrade dependencies and unify error responses
BREAKING CHANGE: drops support for Node 16.
Counts the non-blank lines in a file using the bundled count.py script. Use when asked for an exact line count of a file, where guessing is unacceptable.
Reviews a diff or file for bugs, security issues, and missing tests, returning prioritized findings. Use when the user asks for a code review, a PR review, or "what's wrong with this code".
Writes a Keep a Changelog entry from a description of changes or a git log. Use when the user asks for a changelog entry, release notes, or mentions updating CHANGELOG.md.