mcpField
G
git

git

github.com/maragudkDevelopment4936 installsUpdated 31w ago
Repository

About git

git is a workflow refinement skill for people working with Git branches and commits. It specifies branch naming and commit-message conventions, plus when to ask about issue references and avoid amending commits.

Key features

  1. 01Use short, hyphenated branch names
  2. 02Format code identifiers in backticks
  3. 03Ask about GitHub issue references
  4. 04Use issue-closing phrasing when relevant
  5. 05Avoid amending commits unless instructed

Use cases

  1. 01Name a feature branch
  2. 02Prepare a commit message
  3. 03Reference or close GitHub issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/maragudk/skills --skill git

After installing, type/gitin Claude Code to confirm it loaded.

Details

From the project README

git

Most of git usage is what you already know, so depend on that. This is skill is just a refinement.

Branch naming

Just name the branch a short sentence seperated with dashes. Example: add-some-feature. Don't use feat/, hotfix/ etc. prefixes.

Commit messages

  • Always enclose code identifiers with backticks. Example: "Add html.UserPage component"
  • Always refer to Go code identifiers including the package name, like in html.UserPage above. Fields and methods on structs can be referred with model.User.Name.
  • Ask me about any Github issues that should be referenced. Reference them at the end of the commit message like this: "See #123, #234". If the commit fixes one or more issues, use "Fixes #123, fixes #234" instead (the double "fixes" is important for Github to actually close the issue).
  • Don't mention that you've updated tests, that's assumed.

Committing

  • Don't amend previous commits unless instructed to. When committing after the first commit on a branch, just commit with a simple message (e.g. "fixing …"), because the branch will most times be squashed on Github anyway.

Comments

Markdown supported