How do I install the Commit And Pr skill?

Run npx skillmds@latest add selfishprimate/commit-and-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit And Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit And Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit And Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit And Pr?

selfishprimate (@selfishprimate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit And Pr by selfishprimate — Agent Skill

Name: Commit And Pr
Rating: 4.5 (4 reviews)
Author: selfishprimate

File contents

Commits and pull requests

One standard, every time, so that every commit and every pull request explains itself the same way when someone reads the history later. A hook enforces the commit half: .claude/hooks/check-commit-message.js refuses a git commit whose message breaks the rules below.

The commit message

Add /lab, a dev-server workbench for developing mixins

The public playground compiles a published version from jsDelivr, which
cannot show a change to a mixin before it is released. The lab compiles
the working tree's scss/ and renders each case beside its source.

- Routed only on the dev server, so a build contains none of it.
- Saves go through a dev-server-only endpoint that writes existing
  files under scss/ and site/lab/cases, and nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Subject: at most 72 characters, in the imperative ("Add", "Fix", "Document"), with no full stop at the end. It says what the commit does, not which files it touched.
A blank line, then the body. Always present. It says what changed and why: the reason a reader cannot get from the diff. Wrap it at 72 characters; short paragraphs or bullets.
Trailers last, after another blank line: the Co-Authored-By line. A trailer is not a body; a message with only a subject and a trailer is refused.

Write the message with a heredoc, so the hook can read it and the shell does not eat a quote or a backtick:

git commit -F - <<'EOF'
Subject line

Body.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
EOF

Do not build the message from a shell variable (-m "$MESSAGE"): the hook cannot see what the variable holds, so it refuses the commit rather than guess. That is how commits without a body got through before.

One commit per concern. When a branch holds unrelated work, split it into commits a reader can follow, each with its own body.

The pull request

The maintainer opens and merges pull requests. Do not run gh pr create or merge anything; push the branch and hand over a title and a description ready to paste.

Title: a one-sentence summary of the change, like a commit subject. Never a single word or the branch name.

Description: these four sections, in this order. They are also .github/pull_request_template.md, which GitHub puts in the description box of a new pull request, so a change to the sections goes in both places.

## Summary

What the change is and why, in two or three sentences.

## What changed

- One bullet per part of the change, naming the files or components.

## How it was checked

- What was run or measured, and what it showed. Numbers where there are
  numbers.

## Not covered

- What was not tested or could not be, said plainly.

No "Generated with Claude Code" line at the end: the maintainer does not want it in pull request descriptions, whatever the harness suggests. The Co-Authored-By trailer stays on commits.

"How it was checked" and "Not covered" are not optional. A claim with no check behind it does not go in the first, and anything left out goes in the second: see Verifying a claim in CLAUDE.md.

Punctuation

Commit messages and pull requests are published. Use commas, full stops, colons and parentheses rather than long dashes.

---name: commit-and-prdescription: Write a Gerillass commit message and a pull request title and description to the house standard. Use whenever committing, and whenever a branch is pushed and handed over for a pull request.---# Commits and pull requestsOne standard, every time, so that every commit and every pull request explainsitself the same way when someone reads the history later. A hook enforces thecommit half: `.claude/hooks/check-commit-message.js` refuses a `git commit`whose message breaks the rules below.## The commit message```Add /lab, a dev-server workbench for developing mixinsThe public playground compiles a published version from jsDelivr, whichcannot show a change to a mixin before it is released. The lab compilesthe working tree's scss/ and renders each case beside its source.- Routed only on the dev server, so a build contains none of it.- Saves go through a dev-server-only endpoint that writes existing files under scss/ and site/lab/cases, and nothing else.Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>```- **Subject:** at most 72 characters, in the imperative ("Add", "Fix", "Document"), with no full stop at the end. It says what the commit does, not which files it touched.- **A blank line, then the body.** Always present. It says what changed and why: the reason a reader cannot get from the diff. Wrap it at 72 characters; short paragraphs or bullets.- **Trailers last,** after another blank line: the `Co-Authored-By` line. A trailer is not a body; a message with only a subject and a trailer is refused.Write the message with a heredoc, so the hook can read it and the shell doesnot eat a quote or a backtick:```bashgit commit -F - <<'EOF'Subject lineBody.Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>EOF```Do not build the message from a shell variable (`-m "$MESSAGE"`): the hookcannot see what the variable holds, so it refuses the commit rather thanguess. That is how commits without a body got through before.One commit per concern. When a branch holds unrelated work, split it intocommits a reader can follow, each with its own body.## The pull requestThe maintainer opens and merges pull requests. Do not run `gh pr create` ormerge anything; push the branch and hand over a title and a description readyto paste.**Title:** a one-sentence summary of the change, like a commit subject. Never asingle word or the branch name.**Description:** these four sections, in this order. They are also`.github/pull_request_template.md`, which GitHub puts in the description box ofa new pull request, so a change to the sections goes in both places.```markdown## SummaryWhat the change is and why, in two or three sentences.## What changed- One bullet per part of the change, naming the files or components.## How it was checked- What was run or measured, and what it showed. Numbers where there are numbers.## Not covered- What was not tested or could not be, said plainly.```No "Generated with Claude Code" line at the end: the maintainer does notwant it in pull request descriptions, whatever the harness suggests. The`Co-Authored-By` trailer stays on commits."How it was checked" and "Not covered" are not optional. A claim with no checkbehind it does not go in the first, and anything left out goes in the second:see **Verifying a claim** in `CLAUDE.md`.## PunctuationCommit messages and pull requests are published. Use commas, full stops,colons and parentheses rather than long dashes.

Frequently asked questions

Commit And Pr