What commit message format does it use?

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 72 characters or less with no trailing period, plus an optional body explaining why.

When should changes be split into separate commits?

When the diff does two unrelated things. The skill keeps one logical change per commit, so unrelated work becomes two commits.

How does it open a pull request?

It pushes the branch with git push -u origin , then runs gh pr create, either with --fill or with an explicit title and body. The body states what changed, why, and how it was verified.

Git commits & PRs

SkillCommunication

The git-commit skill is a set of instructions that guides an AI agent through staging files, writing commit messages, and opening pull requests. It covers conventional-commit format, when to split unrelated work into separate commits, and how to push a branch and open a PR with the gh CLI. The agent checks recent commit history first so it matches the repository's existing style.

Connect your AI Use it in a pipeline

Then ask your AI: use the Git commits & PRs skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Make sure git is installed and available on your PATH.

What your AI can do with it

Stage only the files that belong to the current change
Split unrelated work into separate commits
Write conventional-commit messages with an imperative summary
Explain the reasoning behind a change in the commit body
Push a branch and open a pull request with the gh CLI
Match the repository's existing commit style

Getting started

Make sure git is installed and available on your PATH.
Add the skill to your agent so it can read the instructions before committing.
Have the gh CLI installed and authenticated if you want the agent to open pull requests.
Ask the agent to commit your changes or open a pull request.

What this skill tells your AI

The instructions your AI receives, as published by spinabot/brigade in skills/git-commit/SKILL.md and read by Ahel’s review.

Use this when committing changes or opening a pull request.

Before committing

Run git status and git diff --staged to see exactly what's going in. Never git add -A blindly — 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 .gitignore covers 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> then gh 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.

Signals

GitHub stars: 11k
Forks: 70
Last commit: Oct 2026

Questions

What commit message format does it use?: 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 72 characters or less with no trailing period, plus an optional body explaining why.
When should changes be split into separate commits?: When the diff does two unrelated things. The skill keeps one logical change per commit, so unrelated work becomes two commits.
How does it open a pull request?: It pushes the branch with git push -u origin <branch>, then runs gh pr create, either with --fill or with an explicit title and body. The body states what changed, why, and how it was verified.

Advanced

Item type: skill
Key: git-commit-spinabot
Source: github.com/spinabot/brigade

github.com/spinabot/brigade

More in Communication

slack-gif-creator
Skill · anthropics
More in Communication error-handling
Skill · affaan-m
More in Communication emails
Skill · coreyhaines31
More in Communication wait-what
Skill · mattpocock
More in Communication azure-messaging
Skill · microsoft
More in Communication cold-email
Skill · coreyhaines31
More in Communication