CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Repository
aiming-lab/MetaClaw
Path

memory_data/skills/git-workflow/SKILL.md

Commit

922caf3

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill