Agent skill

Common Git

by macalbert in macalbert/envilder

Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

MITAuto-check passedDevelopment

Install Common Git

skills CLI
$ npx skills add macalbert/envilder --skill common-git -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install macalbert/envilder common-git --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/common-git .claude/skills/common-git && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
common-git
GitHub stars
138
Token cost
~991 tokens
SKILL.md length
299 words
Files
2
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

  • Works in 7 steps: Separate subject from body with a blank… → Limit subject line to 50 characters → Capitalize subject line → …
  • Creating commits
  • SKILL.md covers Commit Message Format, Pull Request Workflow, Branching Strategy and Tagging Releases, plus 1 more section
  • Calls git

What it does

Common Git is an agent skill from macalbert/envilder. Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Use when creating commits, pull requests, or managing Git workflow.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Development, covering Git workflow, Commit messages and Pull requests. It works with Git. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

  • Creating commits
  • Managing Git workflow

Example prompts

  • “/common-git”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Separate subject from body with a blank line
  2. Limit subject line to 50 characters
  3. Capitalize subject line
  4. No period at end of subject
  5. Use imperative mood ("add" not "added")
  6. Wrap body at 72 characters
  7. Explain what and why, not how

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Common Git loads about 991 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 299 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~991

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 299 words, ~991 tokens.

Download SKILL.mdSave it as .claude/skills/common-git/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
common-git
description
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Use when creating commits, pull requests, or managing Git workflow.
user-invocable
false

Git Conventions

This skill defines Git commit and PR conventions.

Commit Message Format

Use Conventional Commits format:

xml
<type>(<scope>): <subject>

<body>
Types
  • feat: New feature for the user
  • fix: Bug fix for the user
  • docs: Documentation changes
  • style: Code formatting (no logic changes)
  • refactor: Code refactoring (no behavior changes)
  • test: Adding or updating tests
  • chore: Build process, dependencies, tooling
  • BREAKING CHANGE: Introduces breaking changes
Examples
bash
feat(sdk-dotnet): add Azure Key Vault provider

Implements ISecretProvider for Azure Key Vault using
DefaultAzureCredential. Supports vault URL from $config
and EnvilderOptions override.

Closes #85
bash
fix(cli): correct map file path resolution on Windows

The map file path was not being resolved correctly when using
backslashes. This fix normalizes paths cross-platform.
bash
refactor(core): extract provider factory to shared module

Moves provider selection logic from CLI and GHA startup into
shared ContainerConfiguration for consistency.
Commit Guidelines
  1. Separate subject from body with a blank line
  2. Limit subject line to 50 characters
  3. Capitalize subject line
  4. No period at end of subject
  5. Use imperative mood ("add" not "added")
  6. Wrap body at 72 characters
  7. Explain what and why, not how

Pull Request Workflow

PR Title

Follow same convention as commits:

txt
feat(groups): add collaborative group ownership
PR Description Template
markdown
## Description
Brief description of changes

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update

## Changes Made
- Added X functionality
- Updated Y component
- Fixed Z issue

## Screenshots (if applicable)
![Screenshot](url)

## Checklist
- [ ] Code follows project conventions
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] Build passes locally
- [ ] No breaking changes (or documented)
Merge Strategy

Use Squash and Merge to keep main branch clean:

  • All commits in PR squashed into single commit
  • Commit message follows conventional commits
  • History remains linear and readable

Branching Strategy

Trunk-Based Development
  • main - Production-ready code
  • {usergithub}/{type}/{name} - All work branches (short-lived)
Branch Naming
txt
macalbert/feat/add-azure-provider
macalbert/fix/windows-path-resolution
macalbert/refactor/extract-provider-factory
macalbert/docs/add-nodejs-sdk-references
Workflow
  1. Create branch from main
  2. Make small, frequent commits
  3. Push to remote frequently
  4. Open PR when ready
  5. Get approval from team member
  6. Squash and merge to main
  7. Delete feature branch
  8. Tag release if deploying

Tagging Releases

Use Semantic Versioning:

txt
vMAJOR.MINOR.PATCH
  • MAJOR: Breaking changes
  • MINOR: New features (backward compatible)
  • PATCH: Bug fixes (backward compatible)
Examples tag
bash
# Create tag
git tag -a v2.1.0 -m "Release v2.1.0 - Add group coupons feature"

# Push tag
git push origin v2.1.0

Summary

  • Conventional Commits for all commits
  • Squash and merge for PRs
  • Trunk-based development on main
  • Semantic versioning for releases
  • Short-lived branches (delete after merge)
  • Descriptive PR titles and descriptions

When working with Git:

  1. Use conventional commits format
  2. Write descriptive commit messages
  3. Create focused, small PRs
  4. Get code reviews before merging
  5. Squash and merge to main
  6. Delete branches after merge
  7. Tag releases with semantic versioning

© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .github/skills/common-git of macalbert/envilder.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Common Git next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Common Git compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Common Git this skillmacalbert/envilder138—~991Automated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Adk Gitgoogle/adk-python22k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Adk Git

    google/adk-python

    Official

    Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git PR Flow

    wgzhao/Addax

    Standard branch, commit, and pull-request workflow for this repo.

    1.4k GitHub stars~216 tokensUpdated today
    DevelopmentAuto-check passed

More from macalbert/envilder

All 30 skills in this repo
  • Code Review Perspectives

    macalbert/envilder

    Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

    138 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed
  • Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • Common Testing Conventions

    macalbert/envilder

    Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).

    138 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Doc Maintenance

    macalbert/envilder

    Workflow for maintaining changelogs, READMEs, and documentation files.

    138 GitHub stars~904 tokensUpdated 2 days ago
    Auto-check passed
  • Doc Sync

    macalbert/envilder

    Audit and synchronize documentation across website, READMEs, and docs/.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • Dotnet Test Doubles

    macalbert/envilder

    Test doubles including Fakes (Bogus), Dummies (AutoFixture), Stubs, Spies, and Mocks (NSubstitute).

    138 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Common Git

What does Common Git do?

Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Common Git is an agent skill from macalbert/envilder. Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

When should I use Common Git?

Common Git fits situations like: creating commits; managing Git workflow.

How do I install Common Git in Claude Code?

Run `npx skills add macalbert/envilder --skill common-git -a claude-code`. Or copy the skill folder (.github/skills/common-git in macalbert/envilder) into .claude/skills/common-git in your project. Claude Code loads it when a task matches its description.

How do I install Common Git in Codex?

Run `npx skills add macalbert/envilder --skill common-git -a codex`. Or copy the skill folder (.github/skills/common-git in macalbert/envilder) into .agents/skills/common-git in your project. Codex loads it when a task matches its description.

Can I use Common Git in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill common-git -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/common-git, .gemini/skills/common-git, .github/skills/common-git and .opencode/skills/common-git in your project.

What does Common Git need to run?

Going by SKILL.md and its folder, Common Git needs the command-line tools its instructions call (git). Our summary lists: Node.js.

Does Common Git access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Common Git safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Common Git use?

Common Git is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Common Git use?

About 991 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Common Git?

Skills that share tags, products or a category with Common Git: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Common Git?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.