AI SummaryA personalized git workflow guide that standardizes branch naming, commit message formatting, and code identifier documentation for developers. Benefits teams following specific git conventions and developers using Claude for code commits.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "git" skill in my project. Please run this command in my terminal: # Install skill into the correct directory (12 files) mkdir -p .claude/skills/git && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/SKILL.md "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_ar.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_ar.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_cn.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_cn.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_de.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_de.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_en.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_en.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_es.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_es.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_fr.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_fr.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_it.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_it.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_ja.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_ja.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_ko.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_ko.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_ru.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_ru.txt" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/git/description_tw.txt "https://raw.githubusercontent.com/NeverSight/skills_feed/main/data/skills-md/maragudk/skills/git/description_tw.txt" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Guide for using git according to my preferences. Use it when you're asked to commit something.
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.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster