commit
Quick commit and push with minimal, clean messages
Best use case
commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Quick commit and push with minimal, clean messages
Teams using commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit Compares
| Feature / Agent | commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Quick commit and push with minimal, clean messages
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit Quick commit with conventional message format, then push. ## Context - Git state: !`git status` - Staged changes: !`git diff --cached --stat` - Unstaged changes: !`git diff --stat` - Recent commits: !`git log --oneline -5` - Current branch: !`git branch --show-current` ## Workflow 1. **Analyze**: Review git status - Nothing staged but unstaged changes exist: `git add .` - Nothing to commit: inform user and exit 2. **Generate commit message**: - Format: `type(scope): brief description` - Types: `feat`, `fix`, `update`, `docs`, `chore`, `refactor`, `test`, `perf`, `revert` - Under 72 chars, imperative mood, lowercase after colon - Example: `update(statusline): refresh spend data` 3. **Commit**: `git commit -m "message"` 4. **Push**: `git push` ## Rules - SPEED OVER PERFECTION: Generate one good message and commit - NO INTERACTION: Never ask questions - analyze and commit - AUTO-STAGE: If nothing staged, stage everything - AUTO-PUSH: Always push after committing - IMPERATIVE MOOD: "add", "update", "fix" not past tense
Related Skills
git:commit
Créer des commits bien formatés avec format conventional et emoji
fix-grammar
Fix grammar and spelling errors in one or multiple files while preserving formatting
symfony-framework
Comprehensive Symfony 6.4 development skill for web applications, APIs, and microservices.
symfony:make
Cherche si il existe un maker Symfony pour faire la tache demandée et l'utilise si il existe. Si aucun maker n'existe alors utilise la slash command "/prepare"
phpstan-resolver
Résout automatiquement les erreurs PHPStan en analysant et corrigeant les problèmes de types. Boucle jusqu'à zéro erreur ou stagnation.
elegant-objects
Vérifie la conformité du code PHP aux principes Elegant Objects de Yegor Bugayenko. Analyse un fichier spécifique ou tous les fichiers modifiés dans la branche.
prompt:validate
Vérifie la checklist avant exécution et liste les oublis
prompt:transform
Transforme un prompt en prompt exécutable compatible avec le Task Management System (TaskCreate/TaskUpdate/TaskList)
prompt:team
Orchestre une équipe d'agents spécialisés pour les tâches complexes. Auto-détecte le type, compose l'équipe, coordonne les phases analyse → challenge → implémentation → QA.
prompt:start
Démarre un développement avec un starter léger puis active le mode plan
apex
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.
fix-errors
Fix all ESLint and TypeScript errors with parallel processing using snipper agents