MetaClaw 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.

install

source · Clone the upstream repo

git clone https://github.com/aiming-lab/MetaClaw

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/git-workflow" ~/.claude/skills/aiming-lab-metaclaw-git-workflow && rm -rf "$T"

manifest: memory_data/skills/git-workflow/SKILL.md

source content

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.