engram-commit-hygiene

Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.

Quality

87%

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

100%

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

The body is a tight, actionable standards reference with concrete regexes, type tables, examples, and a pre-commit checklist, well-organized with no padding.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: rules, regexes, type tables, and example blocks with no padding or explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides concrete regexes, explicit rules, and copy-paste-ready valid/invalid examples; as an instruction-only standards skill the actionable guidance is complete despite the absence of code.	3 / 3
Workflow Clarity	A sequenced Pre-Commit Checklist gives unambiguous steps for the single task; per the simple-skill note, a well-organized checklist-based standards skill earns full marks without a validate-fix-retry loop.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the body is a single well-organized document split into clearly labeled sections, satisfying the no-external-references case for full marks.	3 / 3
	Total	12 / 12 Passed

Description

75%

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 clear and complete with explicit trigger guidance, but its capability phrasing and trigger-term coverage are narrower than ideal, costing it on specificity and trigger-term quality.

Suggestions

Broaden trigger terms to natural user phrasings such as 'writing a commit message', 'naming a branch', or 'preparing a PR'.

List a few concrete actions (e.g., 'format commit messages', 'validate branch names', 'clean up staged changes') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('commit and branch naming standards') and enforcement mechanism ('GitHub rulesets') but lists few concrete actions, matching the 'names domain and some actions' anchor rather than multiple specific actions.	2 / 3
Completeness	Explicitly states what the skill does ('commit and branch naming standards...enforced by GitHub rulesets') and provides an explicit 'Trigger:' clause answering when to use it.	3 / 3
Trigger Term Quality	Includes relevant terms ('commit creation', 'review', 'branch cleanup') but the phrasing is somewhat formal and misses common natural variations like 'writing a commit message' or 'naming a branch'.	2 / 3
Distinctiveness Conflict Risk	Scoped to a specific project (Engram) and a narrow naming-standards task with distinct triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	10 / 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: Gentleman-Programming/engram
Path: skills/commit-hygiene/SKILL.md
Commit: 763a6ba

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.