Menu
Use when the user wants a commit message written for currently staged changes. Reads `git diff --cached`, recent log style, and CLAUDE.md, then outputs a conventional-commit-style message โ type(scope) summary + why-focused body.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Use when the user is tired of approving the same routine dev work ("stop asking me yes", "allow the normal dev tools", "grant permissions"). Detects the repo's stack and writes a curated allow-list into the agent's own local permission file so the basics stop prompting โ reading, editing and creating files, plus tests, lint, build, git, the package manager and the run command โ while keeping secret files denied.
Based on SOC occupation classification
| name | fastapi-commit |
| description | Use when the user wants a commit message written for currently staged changes. Reads `git diff --cached`, recent log style, and CLAUDE.md, then outputs a conventional-commit-style message โ type(scope) summary + why-focused body. |
Run git diff --cached --stat and use its output.
Run git diff --cached and use its output.
Run git log --oneline -10 and use its output.
Run git branch --show-current and use its output.
Write a commit message for the changes shown above. Read CLAUDE.md for any project-specific commit conventions before writing.
Format:
<type>(<scope>): <short summary>
<body โ explain what changed and why, not how>
Types: feat, fix, refactor, test, docs, chore, style, perf Scope: the area of code affected (e.g. auth, api, ui)
Rules:
Whatever you output for the user (comments, descriptions, messages) must read as if a human engineer wrote it. These rules mirror klaussy's deterministic humanizer (klaussy-desktop humanize-comment.js):
โ / โ) in prose. Use a comma or rewrite. This is the single biggest AI tell.Same decision, half the words, dropping detail the reader can reconstruct:
Verbose: Good call, done. attachment.reason already embeds the decline reason for declined envelopes (built in checkEnvelopeStatus as {name} declined on {date} - {declinedReason}), so I dropped the new declinedReason signer field and reverted NotificationService to use the existing reason field. Pushed in 1e9e938404.
Human: Good call.
attachment.reasonalready carries the decline reason, so I dropped the new field and reverted NotificationService. Pushed in 1e9e938404.
Output ONLY the commit message, nothing else. Do not wrap it in code blocks.
git commit โ this skill only writes the message text.git add first.