← ClaudeAtlas

fastapi-commitlisted

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.
steph-dove/klaussy-agents · ★ 16 · Code & Development · score 78
Install: claude install-skill steph-dove/klaussy-agents
## Staged changes Run `git diff --cached --stat` and use its output. Run `git diff --cached` and use its output. ## Recent commit style Run `git log --oneline -10` and use its output. ## Current branch Run `git branch --show-current` and use its output. ## Instructions 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: - Summary line under 72 characters. - Body wraps at 80 characters. - Match the style of the recent commits shown above. - Focus on "why" in the body, not "what" (the diff already shows "what"). - If the branch name has a ticket reference (e.g. FEAT-1234), include it in the body. ### Write like a person, not a chatbot 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`): - **No em-dashes or en-dashes** (`—` / `–`) in prose. Use a comma or rewrite. This is the single biggest AI tell. - **No filler openers.** Cut "It's worth noting that", "It's important to note that", "I noticed that", "I wanted to point out that", "Please note that", "Just to mention", "Worth noting", "Note that". State the point directly. - **N