compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.

Quality

84%

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

92%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.

The content is an efficient, actionable, and well-sequenced workflow with strong validation checkpoints for a destructive commit operation. Minor actionability gaps come from cross-references to sibling skills rather than inline steps.

Dimension	Reasoning	Score
Conciseness	The body is a lean, numbered workflow with executable commands and no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	It provides concrete, executable commands (the test-rust-port JSON call, the heredoc git commit) and a clear prefix-detection rule, with minor gaps since /compiler-verify and /compiler-review are referenced rather than inlined.	4 / 5
Workflow Clarity	The 8-step sequence is clearly ordered with explicit validation/stop checkpoints ("Stop on any failure", "stop and do NOT commit") and feedback loops around a destructive commit operation.	5 / 5
Progressive Disclosure	This is a compact, well-organized single-purpose skill under 50 lines with clear Instructions and Examples sections and no external bundle files, meeting the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

76%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.

The description is third-person, concise, and clearly states both what the skill does and when to use it, with concrete actions and an explicit trigger. Trigger-term coverage could be broader with synonyms and file paths.

Dimension	Reasoning	Score
Specificity	"Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix" lists several specific concrete actions with only minor gaps in coverage.	4 / 5
Completeness	It explicitly answers both what ("Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix") and when ("Use when you want to verify compiler changes and commit") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when you want to verify compiler changes and commit" includes relevant natural terms ("compiler changes", "commit") but lacks common synonyms or file-extension variations.	3 / 5
Distinctiveness Conflict Risk	The niche of compiler-change commits with the specific [compiler]/[rust-compiler] prefix is mostly distinct, with only minor overlap risk against generic commit skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: facebook/react
Path: compiler/.claude/skills/compiler-commit/SKILL.md
Commit: 7c6ac13

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.