commits

Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes such as IJ-MR trailers in a final separate paragraph.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured body with concrete examples and clear navigation to canonical references. The only gap is an explicit validation checkpoint embedded in the workflow sequence itself.

Suggestions

Add an explicit validation step to the numbered workflow (e.g., '5. Validate the message via SafePush/Patronus before pushing') so the checkpoint is part of the sequence rather than only mentioned in the critical note.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of git basics Claude already knows; every section (Workflow, Quick Rules, Examples) earns its place.	5 / 5
Actionability	Provides copy-paste-ready commit message examples with subject, body, and IJ-MR trailer, plus an enumerated set of non-production labels and concrete rules a reader can apply directly.	5 / 5
Workflow Clarity	The 4-step workflow is clearly sequenced and validation is flagged via SafePush/Patronus, but an explicit validation checkpoint is not embedded as a workflow step, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to the canonical commit-format doc, an online YouTrack article, and the safe-push skill; content is appropriately split rather than inlined.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that explicitly covers what the skill does and when to use it with natural trigger phrases. Concrete actions and repo-specific framing keep conflict risk low.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "commit changes, write or fix a commit message, amend or rename a commit" — plus format-specific handling (IntelliJ format, full messages, IJ-MR trailers), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both "what" (thin repo-specific overlay using IntelliJ commit format, full messages by default, suffix handling) and "when" ("Use this skill whenever the user asks to commit...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Uses natural user phrasing such as "commit changes", "write or fix a commit message", and "amend or rename a commit" that a user would actually say when requesting this skill.	5 / 5
Distinctiveness Conflict Risk	Scoped to the IntelliJ repository with a repo-specific format overlay, clearly distinguishing it from generic commit skills and minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/commits/SKILL.md
Commit: c74b207

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.