engram-commit-hygiene

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

Quality

85%

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

82%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, highly actionable reference skill with copy-paste regex and thorough valid/invalid examples, capped by a validation checklist. Minor redundancy and a lack of file splitting keep it just short of top marks.

Suggestions

Deduplicate the repeated 'enforced by GitHub ruleset' header suffix into a single statement near the top, since the commit and branch format sections already note enforcement.

Move the allowed-type tables and the valid/invalid example blocks into a references/ file (e.g. FORMATS.md) and link to it, keeping SKILL.md as a concise overview.

Add natural synonyms to the description trigger ('commit message', 'git', 'PR', 'pull request') to broaden keyword coverage.

Dimension	Reasoning	Score
Conciseness	Lean tables, regex, and example blocks assume Claude's competence, but 'enforced by GitHub ruleset' repeats across three headers and the branch type list duplicates the commit table.	4 / 5
Actionability	Copy-paste-ready regex plus comprehensive valid and invalid example sets with per-line explanations give fully executable guidance covering common cases.	5 / 5
Workflow Clarity	A single-purpose, unambiguous task with a Pre-Commit Checklist providing validation checkpoints; no explicit feedback loop is needed for this scope, leaving only minor gaps.	4 / 5
Progressive Disclosure	Well-sectioned single-file structure with clear headers and no nested references, though the type tables and example sets are reference material that could be split into a bundled file.	4 / 5
	Total	17 / 20 Passed

Description

87%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-crafted description that explicitly answers both what and when with concrete trigger phrasing and a distinct, niched scope. Keyword coverage is strong but could add a few common synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain ('commit and branch naming standards') and several concrete actions ('commit creation, review, or branch cleanup'), with only minor coverage gaps.	4 / 5
Completeness	Clearly states what ('commit and branch naming standards… enforced by GitHub rulesets') and an explicit labeled 'when' ('Trigger: Any commit creation, review, or branch cleanup').	5 / 5
Trigger Term Quality	'commit creation, review, or branch cleanup' are natural phrases users would say, though common synonyms like 'commit message', 'git', or 'PR' are absent.	4 / 5
Distinctiveness Conflict Risk	A clear Engram-specific niche with distinct commit/branch-naming triggers and ruleset enforcement, giving minimal overlap with other skills.	5 / 5
	Total	18 / 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: Gentleman-Programming/engram
Path: skills/commit-hygiene/SKILL.md
Commit: 47f281c

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.