Notre avis
Crée des commits Git bien formatés en suivant les standards des commits conventionnels.
Points forts
- Guide l'utilisateur dans le choix du type et de la portée appropriés
- Assure des messages de commit clairs et cohérents
- Facilite la génération automatique de changelog
Limites
- Nécessite que l'utilisateur ait Git configuré
- Ne gère pas automatiquement les conflits de fusion
Utilisez cette compétence lorsque vous devez créer ou écrire des messages de commit pour votre projet.
Ne l'utilisez pas si vous travaillez avec un système de contrôle de version autre que Git.
Analyse de sécurité
PrudenceThe skill uses bash to run typical git operations for staging and committing code. While these are necessary for the stated purpose and not inherently destructive, they can affect the repository state. No exfiltration or obfuscation commands are present.
- •Executes bash commands (git status, diff, add, commit) which could stage or commit unintended changes if misused.
Exemples
I've added a new login feature using Google OAuth. Stage the relevant files and create a commit with a proper conventional commit message.Fix the expired token handling bug in the auth module. The commit message should explain why the change was made.name: commit description: Create well-formatted git commits following conventional commit standards. Use when committing changes, writing commit messages, or asked to commit code.
Commit Skill
Instructions
-
Check Current Status
git status git diff --stat -
Review Changes
git diff # Unstaged changes git diff --staged # Staged changes -
Stage Relevant Files
- Only stage related changes
- Don't mix unrelated changes
-
Determine Commit Type
| Type | When to Use | | ---------- | ------------------------------------- | |
feat| New feature | |fix| Bug fix | |docs| Documentation only | |style| Formatting (no logic change) | |refactor| Code restructure (no behavior change) | |perf| Performance improvement | |test| Adding/updating tests | |build| Build system changes | |ci| CI configuration | |chore| Other (dependencies, etc.) | -
Determine Scope (Optional)
- Feature name:
auth,user,payment - Module name:
api,web,core - Component:
button,modal
- Feature name:
-
Write Commit Message
Commit Message Format
<type>(<scope>): <description>
[optional body]
[optional footer]
Rules
- Use imperative mood: "add" not "added"
- Lowercase first letter
- No period at end
- Max 72 characters for first line
- Body explains WHY, not WHAT
Examples
Simple Commit
git add src/auth/login.ts
git commit -m "feat(auth): add Google OAuth login"
With Body
git commit -m "fix(auth): handle expired token gracefully
The previous implementation threw an unhandled error when tokens expired.
Now we catch the error and redirect to login with a message.
Fixes #123"
Breaking Change
git commit -m "feat(api)!: change user response structure
BREAKING CHANGE: The 'name' field is now split into 'firstName' and 'lastName'.
Migration guide available in docs/migrations/v2.md"
Multiple Files
# Stage related files
git add src/auth/login.ts src/auth/types.ts src/auth/login.test.ts
# One commit for related changes
git commit -m "feat(auth): implement email OTP login
- Add sendOTP function
- Add verifyOTP function
- Add input validation
- Add unit tests"
Anti-Patterns
❌ Bad Commits
# Too vague
git commit -m "fix bug"
git commit -m "update"
git commit -m "WIP"
# Too long
git commit -m "Added new login feature with Google OAuth support and also fixed some bugs in the authentication flow and updated the tests"
# Wrong type
git commit -m "feat: fix login bug" # Should be 'fix'
# Mixed changes
git commit -m "feat: add login and fix navbar and update docs"
✅ Good Commits
# Clear and specific
git commit -m "fix(auth): prevent duplicate OTP requests"
# Proper scope
git commit -m "test(auth): add unit tests for login service"
# Atomic changes
git commit -m "refactor(auth): extract validation to separate module"
Verification
After committing:
# Check commit was created
git log --oneline -1
# Verify files included
git show --stat HEAD
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.