A repository-specific guide for writing and changing commits in the IntelliJ project. A commit is a saved set of code changes with a message explaining what changed and why.

Use it when committing, amending, renaming, or fixing a commit message. It covers reviewing the full diff, choosing the subject, writing the body, and following the project's source documentation.

It helps produce commit messages that meet the project's review and validation rules, including ticket references and explanations for non-trivial changes.

How JetBrains/MPS configures Claude Code and Codex

About the project

JetBrains MPS is a development environment for creating domain-specific languages, which are programming languages designed for a particular field or task. It provides editors with features such as completion, semantic checks, and type checking, and can generate code in languages including Java and XML.

JetBrains/MPS · 1,666 stars · on GitHub · jetbrains.com

Reuse

Borrowing it

Nothing to install: this file belongs to JetBrains/MPS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/JetBrains/MPS/master/.agents/skills/commits/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/JetBrains/MPS

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jetbrains/mps/commits/github.svg)](https://agentmods.dev/skills/jetbrains/mps/commits)

Your own site

<a href="https://agentmods.dev/skills/jetbrains/mps/commits"><img src="https://agentmods.dev/badge/skills/jetbrains/mps/commits/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jetbrains/mps/commits"><img src="https://agentmods.dev/badge/skills/jetbrains/mps/commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 803 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.00803
Opus 5.5	$0.00031	$0.00321
Sonnet 5.5	$0.00016	$0.00161
Haiku 4.5	$0.00008	$0.00080

Measured 2mo ago against content hash b11e9232da3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commits 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 2mo ago.

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.

.agents/skills/commits/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Commits

Critical: SafePush/Patronus validates commit messages before allowing merges. Invalid format wastes CI time and reviewer time.

Workflow

Review the full diff (staged + unstaged) before writing the message.
Identify the motivation: why is this change being made?
Write a subject line: ticket + concise summary (subsystem is not needed when a ticket is present), or label + subsystem + concise summary.
Write a body for any non-trivial change: explain the "why", summarize key design decisions, and note any non-obvious behavioral effects. Do not just restate what the diff shows — explain what the reader cannot see from the code alone.

Source Of Truth

Follow docs/IntelliJ-Platform/0_Intro/2_Commits.md.
This skill is a repo-specific overlay, not a replacement for that document.
In this repository, IntelliJ commit format takes precedence over generic commit conventions.
Do not use Conventional Commits here.
If the user asks to push, use the safe-push skill for push workflow details.

Quick Rules

Behavioral changes need a YouTrack ticket in the subject line.
When a ticket ID is present, omit the subsystem prefix — the ticket provides sufficient context.
Clearly non-behavioral changes may use a non-production label such as tests, cleanup, refactor, docs, format, style, setup, or misc.
If there is any doubt whether the change is behavioral, do not use a non-production label.
Write a full commit message (subject + body) for any non-trivial change. Subject-only is acceptable only for truly mechanical changes (typo, import, format).
The body must explain why the change was made and summarize key decisions. Do not just list what files changed — the diff already shows that.
Keep the first line concise; put rationale and important behavior notes in the body.
If the user requests a suffix such as IJ-MR-100, put it in a final separate paragraph after a blank line.
Do not use commits starting with WIP, fixup!, squash!, or amend!.

Read the full file on GitHub · 76 lines

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.

2mo ago First seen · 76 lines · 78 tokens per session scan A b11e9232da3d

Subscribe to this mod's changes

commits is a skill published in the GitHub repository JetBrains/MPS (1,666 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 803 once invoked, about $0.0003 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-08-30.

Commits Git and workflow domain-specific-language dsl

commits next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
commitsJetBrains/MPS	Skill	1.7k	yesterday	Apache-2.0	A	78	Claude Code, Codex
create-prprisma/orm	Skill	48k	yesterday	Apache-2.0	A	48	Claude Code, Codex
git-commitThinkInAIXYZ/deepchat	Skill	6.4k	yesterday	Apache-2.0	A	15	Claude Code, Codex
engineer-bot-opsmakecindy/cindy	Skill	9.3k	today	Apache-2.0	A	57	Claude Code, Codex
mcore-split-prNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	25	Claude Code
git-commit-writermergisi/awesome-openclaw-agents	Skill	4.1k	2d ago	MIT	A	53	Claude Code, Codex
contributingHugoRCD/evlog	Skill	1.9k	12d ago	MIT	A	68	Claude Code, Codex

MPS: Skill for Claude Code