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

81%

Does it follow best practices?

Impact

56%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is commit in openai/symphony

Quality

Content

85%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 tight, actionable, instruction-only skill body: concrete commands, explicit constraints, validation checkpoints, and a copy-ready template, with no filler. The only refinements worth making are de-duplicating the repeated staging-hygiene checks and showing the here-doc commit-command pattern once.

Dimension	Reasoning	Score
Conciseness	The body is lean with no git-tutorial padding — it gives commands, constraints ("<= 72 characters", "imperative mood"), and a template without explaining concepts Claude already knows. Minor redundancy: steps 4, 5, and 12 each restate the check for unrelated or unexpected files in the index, so it falls just short of anchor 5.	4 / 5
Actionability	Concrete, executable guidance throughout: `git status`, `git diff --staged`, `git add -A`, `git commit -F <file>`, an exact trailer line, and a fill-in template. Anchor 4 rather than 5 because step 11 instructs using a here-doc or temp file but never shows the actual command, leaving one small gap for copy-paste execution.	4 / 5
Workflow Clarity	A clear 12-step numbered sequence with explicit validation checkpoints for a semi-destructive operation: sanity-check newly added files and "flag it to the user before committing" (step 4), "fix the index or ask for confirmation" (steps 5 and 12), and a commit-only-when-message-matches-staged-diff gate (step 12). Validation and error-recovery paths are explicit, so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist and the body references no external paths, so there are no dangling references. This single-purpose skill fits comfortably in one file with clean, well-organized sections (Goals, Inputs, Steps, Output, Template) and no content that should be split out.	5 / 5
	Total	18 / 20 Passed

Description

78%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 well-formed description that clearly states both capability and explicit trigger conditions in third person. Its main weakness is that it names only one concrete action, so capability coverage reads as narrower than the skill's actual scope (message conventions, staging checks, trailers).

Suggestions

Enumerate the concrete capabilities the skill performs, e.g., "Create well-formed git commits: stage intended changes, write conventional type-prefixed messages with summary and rationale, and append co-author trailers."

Add common trigger variations such as "git commit", "make a commit", or "commit message" to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Create a well-formed git commit from current changes using session history for rationale and summary" names the domain and one concrete action with its mechanism, but does not enumerate multiple specific capabilities (e.g., message formatting, staging hygiene, trailers). It is above anchor 2 (generic actions) but below anchor 4 (several specific actions listed).	3 / 5
Completeness	It explicitly answers what ("Create a well-formed git commit from current changes using session history for rationale and summary") and when ("use when asked to commit, prepare a commit message, or finalize staged work") with concrete trigger phrases, matching the anchor 5 example pattern.	5 / 5
Trigger Term Quality	"use when asked to commit, prepare a commit message, or finalize staged work" covers natural phrases users would say ("commit", "commit message", "staged"), but misses common variations such as "git commit", "make a commit", or "check in changes". Good coverage with a few natural terms missing, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	The commit-message niche with triggers like "commit message" and "staged" is mostly distinct from other skills, with only minor overlap risk against generic git-workflow or code-review skills — anchor 4 rather than 5 because it is not a fully isolated niche.	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: karanhudia/borg-ui
Path: .codex/skills/commit/SKILL.md
Commit: 47dfb3e

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.