git-workflow
Use this skill when working with git — making commits, creating branches, resolving merge conflicts, opening pull requests, or reviewing diffs. Apply whenever the user asks about version control operations.
Datos de origen
- Repositorio
- aiming-lab/MetaClaw
- Última actividad en el origen
- 10 de marzo de 2026 a las 18:04
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 3456
- Forks
- 450
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- git-workflow
- description
- Use this skill when working with git — making commits, creating branches, resolving merge conflicts, opening pull requests, or reviewing diffs. Apply whenever the user asks about version control operations.
- category
- coding
# Git Workflow Best Practices
**Commits:**
- Write commit messages in imperative mood: `Add feature X`, not `Added feature X`.
- One logical change per commit. Do not bundle unrelated changes.
- Stage specific files (`git add <file>`), not `git add .` blindly.
**Branches:**
- Branch from the latest main/master: `git checkout -b feature/my-change`.
- Keep branches short-lived; merge or rebase frequently.
**Pull Requests:**
- Include a short description of *why*, not just *what*.
- Reference related issues (`Closes #123`).
- Keep PRs focused — one feature or fix per PR.
**Never:** force-push to shared branches, skip hooks with `--no-verify`, or commit secrets.
Ver en GitHub