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.
Sets habits for staging deliberately, writing Conventional Commit messages, keeping one change per commit and opening pull requests with the gh CLI.
Install Git Commits and Pull Requests
$ npx skills add spinabot/brigade --skill git-commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spinabot/brigade git-commit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/git-commit .claude/skills/git-commit && rm -rf skills-srcUse ~/.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/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .claude/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/spinabot/brigade/tree/main/skills/git-commitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add spinabot/brigade --skill git-commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spinabot/brigade git-commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/git-commit .agents/skills/git-commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .agents/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spinabot/brigade --skill git-commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spinabot/brigade git-commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/git-commit .cursor/skills/git-commit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .cursor/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/spinabot/brigade.git --path skills/git-commit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add spinabot/brigade --skill git-commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spinabot/brigade git-commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/git-commit .gemini/skills/git-commit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .gemini/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install spinabot/brigade git-commitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add spinabot/brigade --skill git-commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/git-commit .github/skills/git-commit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .github/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spinabot/brigade --skill git-commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install spinabot/brigade git-commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spinabot/brigade.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/git-commit .opencode/skills/git-commit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "git-commit" agent skill from https://github.com/spinabot/brigade/tree/main/skills/git-commit into .opencode/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
git-commit- GitHub stars
- 11k
- Token cost
- ~390 tokens
- SKILL.md length
- 177 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sets habits for staging deliberately, writing Conventional Commit messages, keeping one change per commit and opening pull requests with the gh CLI.
- Committing a set of changes that should be split into logical commits
- SKILL.md covers Before committing, Message format, Pull requests (gh CLI) and Conventions to honor
- Calls git and gh
- Writing a commit message in Conventional Commits format
What it does
Before anything is committed, this skill has the agent look at git status and the staged diff, stage only the files that belong to the change instead of adding everything, split unrelated edits into separate commits, and make sure secrets, large binaries and generated artifacts are kept out via .gitignore.
Messages follow Conventional Commits: a type such as feat, fix, docs, refactor, test, chore, perf, build or ci, an optional scope, and a short imperative summary of at most 72 characters with no trailing period. The body should record why the change was made, not repeat the diff. For pull requests the agent pushes the branch and runs gh pr create, writes a description covering what changed, why and how it was verified, and confirms the base branch first. If recent history in git log uses another format, the repository's convention wins.
When your agent uses it
- Committing a set of changes that should be split into logical commits
- Writing a commit message in Conventional Commits format
- Opening a pull request with a clear description of what changed and how it was tested
Example prompts
- “Commit my changes, splitting the refactor from the bug fix into two commits.”
- “Write a conventional commit message for the staged diff and explain why in the body.”
- “Push this branch and open a pull request against main with a short test summary.”
Requirements
- Git
- The GitHub CLI (gh) for opening pull requests
What it can do on your machine
Read from SKILL.md and the folder at commit 4c2a18f. 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:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Git Commits and Pull Requests loads about 390 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 177 words of instructions outside code blocks.
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 spinabot/brigade at commit 4c2a18f, republished under its MIT licence (© spinabot). 177 words, ~390 tokens.
Download SKILL.mdSave it as
.claude/skills/git-commit/SKILL.md (or your agent's skills folder).- name
- git-commit
- description
- Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
- requires-bins
- git
Git commits & PRs
Use this when committing changes or opening a pull request.
Before committing
- Run
git statusandgit diff --stagedto see exactly what's going in. Nevergit add -Ablindly — stage the files that belong to this change. - Keep one logical change per commit. If the diff does two unrelated things, make two commits.
- Don't commit secrets, large binaries, or generated artifacts. Check
.gitignorecovers them.
Message format
Conventional Commits:
<type>(<optional scope>): <short imperative summary>
<optional body — what changed and WHY, wrapped at ~72 cols>Types: feat, fix, docs, refactor, test, chore, perf, build, ci.
- Summary in the imperative mood ("add", not "added"), ≤72 chars, no trailing period.
- The body explains the reasoning a future reader needs — not a restatement of the diff.
Pull requests (gh CLI)
git push -u origin <branch>thengh pr create --fill(or--title/--body).- PR body: what changed, why, and how it was verified (tests run, manual checks).
- Confirm the base branch is correct before creating.
Conventions to honor
Match the repository's existing style — read recent git log --oneline first and follow whatever format the project already uses if it differs from the above.
© spinabot, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/git-commit of spinabot/brigade.
Open the folder on GitHubat commit 4c2a18f
Compare with similar skills
Git Commits and Pull Requests 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Git Commits and Pull Requests this skillspinabot/brigade | 11k | — | ~390 | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Adk Gitgoogle/adk-python | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
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.
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.
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.
- Official
Adk Git
google/adk-python
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…
Git PR Flow
wgzhao/Addax
Standard branch, commit, and pull-request workflow for this repo.
More from spinabot/brigade
All 11 skills in this repoCanvas Display
spinabot/brigade
Shows HTML content such as games, dashboards, visualizations and demos on a connected Brigade node's canvas, using a local canvas host server and a node bridge.
Word Document Builder
spinabot/brigade
Creates and edits Word documents along four paths of rising capability, from a quick tool to the docx library, an OOXML round-trip and pandoc, then verifies the file.
HyperFrames Video Compositions
spinabot/brigade
Writes HTML compositions with a GSAP timeline that the render_video tool turns into deterministic MP4 videos from data, text or layouts.
Brigade Node Connection Diagnostics
spinabot/brigade
Diagnoses why a Brigade companion app can't pair or connect, by first identifying the real node-to-gateway route and then fixing auth.
OAuth Account Setup
spinabot/brigade
Connects an OAuth 2.0 account such as Gmail with the built-in oauth_authorize tool: an authorization link, automatic code capture and sealed token storage.
Brigade PDF Toolkit
spinabot/brigade
Creates and edits PDFs in Brigade through four paths: a quick content tool, an edit tool for forms and merging, a pdf-lib script for full control, and HTML-to-PDF for styled layouts.
Related
Works with
Categories
Questions about Git Commits and Pull Requests
What does Git Commits and Pull Requests do?
Sets habits for staging deliberately, writing Conventional Commit messages, keeping one change per commit and opening pull requests with the gh CLI. gitignore.
When should I use Git Commits and Pull Requests?
Git Commits and Pull Requests fits situations like: committing a set of changes that should be split into logical commits; writing a commit message in Conventional Commits format; opening a pull request with a clear description of what changed and how it was tested.
How do I install Git Commits and Pull Requests in Claude Code?
Run `npx skills add spinabot/brigade --skill git-commit -a claude-code`. Or copy the skill folder (skills/git-commit in spinabot/brigade) into .claude/skills/git-commit in your project. Claude Code loads it when a task matches its description.
How do I install Git Commits and Pull Requests in Codex?
Run `npx skills add spinabot/brigade --skill git-commit -a codex`. Or copy the skill folder (skills/git-commit in spinabot/brigade) into .agents/skills/git-commit in your project. Codex loads it when a task matches its description.
Can I use Git Commits and Pull Requests 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 spinabot/brigade --skill git-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-commit, .gemini/skills/git-commit, .github/skills/git-commit and .opencode/skills/git-commit in your project.
What does Git Commits and Pull Requests need to run?
Going by SKILL.md and its folder, Git Commits and Pull Requests needs the command-line tools its instructions call (git and gh). Our summary lists: Git; The GitHub CLI (gh) for opening pull requests.
Does Git Commits and Pull Requests access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Git Commits and Pull Requests 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 Git Commits and Pull Requests use?
Git Commits and Pull Requests 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 Git Commits and Pull Requests use?
About 390 tokens (SKILL.md is roughly 1.6k 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 Git Commits and Pull Requests?
Skills that share tags, products or a category with Git Commits and Pull Requests: Git Workflow and Versioning (addyosmani/agent-skills, 103k 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 Git Commits and Pull Requests?
spinabot (a GitHub organization) maintains it in spinabot/brigade, which has 11,284 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.
Source: spinabot/brigade on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.