commit

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

1.00x

Quality

95%

Does it follow best practices?

Impact

56%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

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

A tight, actionable, well-sequenced skill body with explicit validation feedback loops for a destructive operation and no external-reference overhead. It is an example of an efficient single-purpose skill.

Dimension	Reasoning	Score
Conciseness	Lean, sectioned content with no concept padding; every section earns its place, and the repeated staging-safety checks serve the destructive nature of a commit rather than adding fluff.	3 / 3
Actionability	Provides concrete commands (git status/diff/diff --staged, add -A, commit -F), explicit subject/body rules (imperative, <=72 chars, no trailing period, 72-wrap), and a copy-paste-ready template.	3 / 3
Workflow Clarity	A clearly sequenced 12-step flow with explicit validation checkpoints: flag random/ignored files, fix or confirm incomplete staging, and commit only when the message matches the staged diff.	3 / 3
Progressive Disclosure	A single self-contained file with well-organized sections and no nested references, which is appropriate for a single-purpose skill with no need for external detail.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-targeted description that answers both what and when with natural trigger terms and low conflict risk. Specificity is the only soft spot, since it elaborates one action rather than enumerating several concrete ones.

Suggestions

To raise specificity, enumerate a few distinct concrete actions — e.g., 'inspect staged diffs, draft conventional-commit subjects and 72-wrapped bodies, append co-author trailers' — instead of stating one elaborated action.

Consider adding the natural trigger 'write a commit message' verbatim alongside 'prepare a commit message' to match an even wider range of user phrasings.

Dimension	Reasoning	Score
Specificity	Names the git-commit domain and concretely ties the output to session-history rationale/summary, but it describes a single primary action rather than listing multiple distinct concrete actions.	2 / 3
Completeness	Explicitly answers what it does (create a well-formed commit using session history for rationale and summary) and when to use it via an explicit 'use when' clause.	3 / 3
Trigger Term Quality	Uses natural phrasing a user would actually say — 'commit', 'prepare a commit message', 'finalize staged work' — giving good coverage of common request variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (git commits) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: openai/symphony
Path: .codex/skills/commit/SKILL.md
Commit: f8e8b8a

Reviewed: 6 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.