git-conventional-commit
Create clean git commits using the Conventional Commits format (type(scope): summary). Use when Codex needs to stage changes, craft commit messages, and record completed work in a Git repository.
Informations de source
- Dépôt
- nibzard/looper-go
- Dernière activité de la source
- 21 janvier 2026 à 12:36
- Langue détectée de SKILL.md
- anglais
- Étoiles
- 5
- Forks
- 0
Options d'installation
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Vérifiez les fichiers source
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Affichage de SKILL.md
SKILL.md
Instructions source · Aperçu en lecture seule- name
- git-conventional-commit
- description
- Create clean git commits using the Conventional Commits format (type(scope): summary). Use when Codex needs to stage changes, craft commit messages, and record completed work in a Git repository.
# Git Conventional Commit
## Overview
Create one conventional commit per completed task while keeping the working tree clean and history stable.
## Workflow
1. Review changes with `git status` and `git diff`.
2. Stage only the changes related to the task (use `git add -A` or selective adds).
3. Compose a Conventional Commit message: `type(scope): summary`.
- Types: feat, fix, refactor, docs, test, chore, build, ci, perf, style.
- Use imperative mood and keep the summary under 72 characters.
4. Commit once per task. Do not amend, rebase, or rewrite history.
5. If there are no changes to commit, skip the commit and report why.
## Notes
- Avoid touching unrelated changes in a dirty working tree.
- Prefer a specific scope (folder or subsystem) when it clarifies intent.
Voir sur GitHub