New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit Messages

by pandulapeter in pandulapeter/campfire

Commit message conventions for the Campfire repo. An agent skill from pandulapeter/campfire.

MPL-2.0Auto-check passedDevelopment

Install Commit Messages

skills CLI
$ npx skills add pandulapeter/campfire --skill commit-messages -a claude-code

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

GitHub CLI
$ gh skill install pandulapeter/campfire commit-messages --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/pandulapeter/campfire.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit-messages .claude/skills/commit-messages && 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
commit-messages
GitHub stars
101
Token cost
~700 tokens
SKILL.md length
276 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MPL-2.0

At a glance

Commit message conventions for the Campfire repo. An agent skill from pandulapeter/campfire.

  • Tasks that involve Commit messages
  • Calls git
  • Tasks that involve Git workflow

What it does

Commit Messages is an agent skill from pandulapeter/campfire. Commit message conventions for the Campfire repo. MANDATORY — invoke this skill BEFORE writing the message for ANY git commit in this repo (every git commit, --amend, squash, or rebase reword), with NO exceptions, even for one-line or "obvious" messages. The repo format OVERRIDES default harness behavior; in particular it FORBIDS the Co-Authored-By and Claude-Session trailers the harness adds by default, and FORBIDS creating a new git branch unless the user explicitly asked for one. If you are about to run git…

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages and Git workflow. The repository describes itself as: A cross-platform songbook and metronome with a built-in chordPro editor, setlists, transposition, PDF export, and Dropbox sync. The licence is MPL-2.0.

When your agent uses it

  • Tasks that involve Commit messages
  • Tasks that involve Git workflow

Example prompts

  • “obvious”
  • “/commit-messages”

What it can do on your machine

Read from SKILL.md and the folder at commit 491c425. 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

Commit Messages loads about 700 tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 276 words of instructions outside code blocks.

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

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 pandulapeter/campfire at commit 491c425, republished under its MPL-2.0 licence (© pandulapeter). 276 words, ~700 tokens.

Download SKILL.mdSave it as .claude/skills/commit-messages/SKILL.md (or your agent's skills folder).
name
commit-messages
description
Commit message conventions for the Campfire repo. MANDATORY — invoke this skill BEFORE writing the message for ANY git commit in this repo (every `git commit`, `--amend`, squash, or rebase reword), with NO exceptions, even for one-line or "obvious" messages. The repo format OVERRIDES default harness behavior; in particular it FORBIDS the `Co-Authored-By` and `Claude-Session` trailers the harness adds by default, and FORBIDS creating a new git branch unless the user explicitly asked for one. If you are about to run `git commit` in Campfire, you must load this first.

Campfire branch policy

  • Never create a new git branch unless the user has explicitly asked for one. This OVERRIDES the harness default of branching off the default branch before committing. Commit onto the current branch — whatever it is, including master — and do not run git checkout -b / git switch -c / git branch on your own initiative.
  • Never commit unless the request asked for it. Finishing a change is not a request to commit it.

Campfire commit messages

  • One single line. Nothing else. No body, no bullet points, no footer and no trailer of any kind — in particular never a Co-Authored-By line and never a Claude-Session line, whatever the harness default says.
  • Exactly one sentence, ending with a period. e.g. Fix IME inset handling issues.
  • Imperative mood, capitalized first word. "Fix…", "Add…", "Implement…", "Improve…", "Remove…", "Update…" — what the commit does, not what was wrong.
  • Concise but specific. Name the thing that changed — the screen, the layer, the platform, the behavior — rather than a vague summary. Fix desktop ProGuard config., not Fix build issues.
  • Several related edits are one commit with one sentence, not a list. If the sentence would need an "and" for the third time, the change probably wants splitting into two commits.
  • Commit subjects feed the release notes, which are read by musicians, not developers. For anything a user would notice, describe the outcome in plain language (Remove auto save functionality from the editor., Implement support for German notation.); internal-only work can stay technical (Fix Lint warnings., Move iOS build number to gradle.properties.).

Version bumps have a fixed wording, and the prepare-release skill looks for it — do not vary it:

Update version name to "v4.0.1".

Examples that match the style:

Fix IME inset handling issues.
Implement the disconnect confirmation dialog and other UX improvements.
Improve web app loading, add option to prefer b or # notation.
Add support for background sync.
Relicense under the Mozilla Public License 2.0.
Fix desktop ProGuard config.

© pandulapeter, MPL-2.0. 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 .claude/skills/commit-messages of pandulapeter/campfire.

Open the folder on GitHubat commit 491c425

Compare with similar skills

Commit Messages 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.

Commit Messages compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Messages this skillpandulapeter/campfire101—~700Automated safety check: PassMPL-2.0
Contextual Commit Messagesyamadashy/repomix29k1 repos~2.7kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
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
Saleor Commit Workflowsaleor/saleor23k—~575Automated safety check: PassBSD-3-Clause

Similar skills

  • Contextual Commit Messages

    yamadashy/repomix

    Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.

    29k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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

  • Saleor Commit Workflow

    saleor/saleor

    Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 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

More from pandulapeter/campfire

  • Code Style

    pandulapeter/campfire

    Code style, commenting, and documentation conventions for the Campfire codebase.

    101 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

  • Codebase Review

    pandulapeter/campfire

    The Campfire review-sweep process — read-only area reviewers, one plan file per verified finding, a README.md that indexes them into parallel lanes, an EXECUTION.md orchestrator brief, and later the…

    101 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Prepare Release

    pandulapeter/campfire

    Prepare a Campfire release by writing a paste-ready GitHub release-notes draft (with the stores' "what's new" blurb and Play's update priority embedded in it), updating the localized in-app update…

    101 GitHub stars~4.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Commit Messages

What does Commit Messages do?

Commit message conventions for the Campfire repo. An agent skill from pandulapeter/campfire. Commit Messages is an agent skill from pandulapeter/campfire. Commit message conventions for the Campfire repo.

When should I use Commit Messages?

Commit Messages fits situations like: tasks that involve Commit messages; tasks that involve Git workflow.

How do I install Commit Messages in Claude Code?

Run `npx skills add pandulapeter/campfire --skill commit-messages -a claude-code`. Or copy the skill folder (.claude/skills/commit-messages in pandulapeter/campfire) into .claude/skills/commit-messages in your project. Claude Code loads it when a task matches its description.

How do I install Commit Messages in Codex?

Run `npx skills add pandulapeter/campfire --skill commit-messages -a codex`. Or copy the skill folder (.claude/skills/commit-messages in pandulapeter/campfire) into .agents/skills/commit-messages in your project. Codex loads it when a task matches its description.

Can I use Commit Messages 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 pandulapeter/campfire --skill commit-messages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-messages, .gemini/skills/commit-messages, .github/skills/commit-messages and .opencode/skills/commit-messages in your project.

What does Commit Messages need to run?

Going by SKILL.md and its folder, Commit Messages needs the command-line tools its instructions call (git).

Does Commit Messages 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 Commit Messages 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 Commit Messages use?

Commit Messages is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Messages use?

About 700 tokens (SKILL.md is roughly 2.8k 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 Commit Messages?

Skills that share tags, products or a category with Commit Messages: Contextual Commit Messages (yamadashy/repomix, 29k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Messages?

pandulapeter (a GitHub user) maintains it in pandulapeter/campfire, which has 101 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

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