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.
Source facts
- Repository
- aiming-lab/MetaClaw
- Last source activity
- March 10, 2026 at 18:04
- Detected SKILL.md language
- English
- Stars
- 3,456
- Forks
- 450
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- 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.
View on GitHub