New: 98,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 PR

by ahmetb in ahmetb/dotfiles

How to name branches, writing commit titles/messages and sending PRs with correct format

Apache-2.0Auto-check passedDevelopment

Install Commit PR

skills CLI
$ npx skills add ahmetb/dotfiles --skill commit-pr -a claude-code

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

GitHub CLI
$ gh skill install ahmetb/dotfiles commit-pr --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/ahmetb/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit-pr .claude/skills/commit-pr && 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-pr
GitHub stars
139
Token cost
~1.1k tokens
SKILL.md length
504 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

How to name branches, writing commit titles/messages and sending PRs with correct format

  • Works in 2 steps: add a line after commit description/PR… → ensure the PR/commit title mentions the…
  • Tasks that involve Commit messages
  • SKILL.md covers Branch names, Commit messages/titles, PR title/description and PR/Commit Message Styling, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Commit PR is an agent skill from ahmetb/dotfiles. How to name branches, writing commit titles/messages and sending PRs with correct format

Its SKILL.md is about 1.1k 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. The repository describes itself as: Ahmet's dotfiles and macOS customizations. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/commit-pr”

Workflow steps

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

  1. add a line after commit description/PR summary saying Fixes FOO-123. and
  2. ensure the PR/commit title mentions the [FOO-123] on its title, e.g.

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 PR loads about 1.1k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 504 words of instructions outside code blocks.

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

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 ahmetb/dotfiles at commit a435fa0, republished under its Apache-2.0 licence (© ahmetb). 504 words, ~1,066 tokens.

Download SKILL.mdSave it as .claude/skills/commit-pr/SKILL.md (or your agent's skills folder).
name
commit-pr
description
How to name branches, writing commit titles/messages and sending PRs with correct format

Branch names

  • All git branches should start with ahmet/

Commit messages/titles

  • Keep commit titles short if possible (like Linux kernel patches)

  • Do not make commits with just title+bug number; add a short explanation that is a summary of the PR description.

  • Use conventionalcommits style when possible and pragmatic in commit titles (you can sometimes omit the component name). Look at the last PRs in the repo to understand the convention but err on the side of conventionalcommits.

  • Do not be super specific in commit messages, don't mention stuff like method names, variable names etc. Focus on why we did this commit and what problem we are solving.

  • If there's a Linear ticket (e.g. FOO-123) in the context of this PR:

    1. add a line after commit description/PR summary saying Fixes FOO-123. and link to the Linear bug (if link isn't present in context, use http://go/issue/FOO-123) as a markdown link in PR description, and just as bare text of bug ID no URL in commit message. if this doesn't close the issue, just mention that it's related.
    2. ensure the PR/commit title mentions the [FOO-123] on its title, e.g. feat(api): [FOO-123] add new functionality.

PR title/description

Try to preserve commit titles as PR titles as much as possible.

IT IS VERY IMPORTANT YOU USE A COMBINATION OF WRITING STYLE:

  1. ASD-STE100 Simplified Technical English
  2. Orwell's rules
  3. GOV. UK house style
  4. Willem Zinsser of "On Writing Well" to redpen it.

Organize PR description as follows (keep h2 titles):

## Rationale

<why are we making this change, what is it ultimately for>
<if there are any work tickets, link here>

## Summary

<high-level explain functionally what's changed in the system>
<someone who's new to the component should be able to understand how we changed to this system>
<do not go into specifics like method/type names>
<the section below has more tips on wording>

## Testing

<if there are important callouts like migrations / changes that need to be done
 in lockstep, mention them here>
<explain how we'll validate this change, or mention if we've added tests, keep
it brief. if we're relying on existing test execution in the CI pipeline, just
mention that>

See next section for more:

Show full SKILL.md (250 more words)Show less

PR/Commit Message Styling

You are an expert at writing clear, concise pull request descriptions and commit messages. Your goal is to help reviewers understand what the change accomplishes without overwhelming them.

Principles

  • Describe WHAT the change delivers, not the implementation details or how it works
  • Keep it high-level. Reviewers can examine diffs for technical specifics
  • Assume reviewers are intelligent and busy — respect their time
  • Only surface file names, functions, or code details if there's a specific reason reviewers should scrutinize them (e.g., complex logic, edge cases, security concerns, architectural decisions)

Include

  • The problem being solved or feature being added
  • The user-facing or system-level impact
  • Any key context (related issues, dependencies, breaking changes)
  • Callouts for areas needing careful review (if applicable)

Skip

  • Line-by-line changes
  • Implementation approach or design patterns used
  • Obvious refactoring details
  • Generic function names or file paths (unless there's a reason to highlight them)

Format

Write a clean, scannable description — 2–4 sentences is often perfect. Use bullet points only if there are multiple distinct deliverables or important callouts.

Confirmation step for commit/PRs

Before sending a PR show me the title/description and also you're using in a nice way and let me approve or edit in a prompt.

PR stacks

If the PRs are stacked, make sure each PR has a section like this that marks the current PR.

## PR Stack

1. <link to PR>
2. this PR

and if a PR is not ready to review, make sure a PR stays in Draft, and it has a description that begins like the following until the PR is ready:

> [!WARNING]
> This PR is part of a stack, please review [previous PRs](link to previous pr) first.

© ahmetb, Apache-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-pr of ahmetb/dotfiles.

Open the folder on GitHubat commit a435fa0

Compare with similar skills

Commit PR 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 PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit PR this skillahmetb/dotfiles139—~1.1kAutomated safety check: PassApache-2.0
Contextual Commit Messagesyamadashy/repomix29k1 repos~2.7kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Caveman Commitvishiri/fantasia-archive40913 repos~642Automated safety check: PassGPL-3.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0

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

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Caveman Commit

    vishiri/fantasia-archive

    Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 13 repos~642 tokens
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    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 today
    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.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from ahmetb/dotfiles

  • Here Now

    ahmetb/dotfiles

    USE THIS SKILL ONLY ON PUBLIC OPEN SOURCE REPOS!!!. An agent skill from ahmetb/dotfiles.

    139 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

  • Here Now Internal

    ahmetb/dotfiles

    Upload and share files on here.now (https://here-now.chimera-logarithm.ts.net), Baseten's internal artifact-sharing service.

    139 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Sweep Comments

    ahmetb/dotfiles

    Hold code comments and docstrings to a strict quality bar. An agent skill from ahmetb/dotfiles.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Declaudish

    ahmetb/dotfiles

    Translate text written in "Claudish" — the characteristic prose style of Claude and Claude Code — into plain, direct, idiomatic English.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Report Styling

    ahmetb/dotfiles

    Design system for single-file HTML engineering reports and deep dives — two-column sticky-TOC layout, green-accented semantic color coding, timeline step lists, code-anchored prose.

    139 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Commit PR

What does Commit PR do?

How to name branches, writing commit titles/messages and sending PRs with correct format. Commit PR is an agent skill from ahmetb/dotfiles.

When should I use Commit PR?

Commit PR fits situations like: tasks that involve Commit messages.

How do I install Commit PR in Claude Code?

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

How do I install Commit PR in Codex?

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

Can I use Commit PR 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 ahmetb/dotfiles --skill commit-pr -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-pr, .gemini/skills/commit-pr, .github/skills/commit-pr and .opencode/skills/commit-pr in your project.

What does Commit PR need to run?

SKILL.md names no scripts, command-line tools or credentials: Commit PR is instructions for the agent only.

Does Commit PR access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Commit PR 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 PR use?

Commit PR is published under the Apache-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 PR use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 PR?

Skills that share tags, products or a category with Commit PR: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Caveman Commit (vishiri/fantasia-archive, 409 stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit PR?

ahmetb (a GitHub user) maintains it in ahmetb/dotfiles, which has 139 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 24, 2026.

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