cratis-commits-and-pull-requests

cratis-commits-and-pull-requests is a skill for Claude Code, Codex from Cratis/AI. It costs 105 tokens per session (630 once invoked), scanned A, original, MIT.

A guide for preparing Git commits and pull requests, which are proposed sets of repository changes for review. It covers commit boundaries, consumer-facing release notes, issue references, labels, and required checks.

In plain words
What is it for?
Use it to inspect and stage specific changes, write commit messages, prepare pull-request descriptions, choose release intent, reference completed issues, and run the required checks.
Why use it?
Poorly grouped commits and unclear pull requests make changes harder to review and release. The guide helps keep history coherent and prevents unsupported release claims.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect and stage specific changes, write commit messages, prepare pull-request descriptions, choose release intent, reference completed issues, and run the required checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cratis/ai/cratis-commits-and-pull-requests
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Cratis/AI --skill cratis-commits-and-pull-requests
Clone the repo
git clone --depth 1 https://github.com/Cratis/AI

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cratis-commits-and-pull-requests

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-commits-and-pull-requests/github.svg)](https://agentmods.dev/skills/cratis/ai/cratis-commits-and-pull-requests)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-commits-and-pull-requests"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-commits-and-pull-requests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cratis-commits-and-pull-requests

Your own site · 80×15
<a href="https://agentmods.dev/skills/cratis/ai/cratis-commits-and-pull-requests"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-commits-and-pull-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00105 $0.00630
Opus 5.5 $0.00042 $0.00252
Sonnet 5.5 $0.00021 $0.00126
Haiku 4.5 $0.00011 $0.00063

Measured today against content hash 31de14111449, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cratis-commits-and-pull-requests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cratis/ai/skills/cratis-commits-and-pull-requests/SKILL.md · 49 lines

What it actually says

Commits and pull requests

Read git-commits.md and pull-requests.md before acting. Their always-on contracts govern history, release notes, labels, authority and required gates. Loading this skill grants no permission to push, publish, merge or mutate issues.

  1. Inspect the diff and the repository's workflow before choosing the logical commit boundaries and release intent. Read references/commits.md when staging, writing a message or deciding when to commit. Stage specific files and inspect git diff --cached; never commit an unbuildable unit.
  2. Read references/pr-description.md when writing or editing a PR or manual release note. Write consumer-facing bullets, not a work report. Only fully delivered issues get a closing delivery reference.
  3. Read references/pr-labels-and-release.md when choosing or swapping a label, grouping related work, checking gates or handling a release-action window. Confirm publication effects before applying the single label. A human confirms and merges a major release.
  4. Run affected-project gates, then the repository-required checks. Before each body edit, compare git diff --stat origin/main...HEAD and remove unsupported bullets. Validate the description with node .cratis/ai/hooks/scripts/cratis-check-pr.mjs --body-file <file> --label <intent>. A zero exit status is the pass signal; fix the description on failure.
  5. Create or edit only when authorized. Put verification, review and deployment notes in a PR comment, not the published release note. Confirm the applied label and body after writing. Never replace history for a tidier PR.

Minimal description for a delivered consumer fix without an issue reference:

## Fixed

- Preserve command validation messages when a request is retried.

If the diff only changes non-outward documentation or tooling, choose no-release rather than manufacturing a patch release. If the workflow or impact is unclear, ask about that specific choice rather than guessing.

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 49 lines · 105 tokens per session scan A 31de14111449

Subscribe to this mod's changes

cratis-commits-and-pull-requests is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 630 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.