gerrit-hygiene-operations

Provides rules, patterns, and best practices for code hygiene, formatting, downstream plugin dependencies, and release operations in Gerrit.

Quality

49%

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

Fix and improve this skill with Tessl

tessl review fix ./configs/skills/gerrit_hygiene_operations/SKILL.md

Quality

Content

50%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 guide is well-structured into chapters with concrete Don't/Do examples for most rules, making it reasonably actionable. However, it is noticeably verbose with redundant restatement across the summary table, context, and rule blocks, and it is a monolithic single-file reference with no progressive disclosure to separate files or validation checkpoints for destructive operations.

Suggestions

Trim the Executive Summary and remove redundant restatement between the summary table, each chapter's Context, and the Rule/What/Why blocks; keep only what Claude cannot infer.

Add explicit validation/verification steps for destructive operations (e.g., after deleting decommissioned fallbacks in T5-01, run lint/build and confirm no remaining references before submitting).

Split the seven chapters into one-level-deep reference files (e.g., references/formatting.md, references/release-notes.md) linked from a concise overview in SKILL.md to improve progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The Executive Summary is heavily padded with buzzwords ("authoritative engineering guide", "living repository", "definitive source of tribal knowledge", "fortifies the integrity"), and the summary table, Context, and Rule/What blocks redundantly restate the same content across every chapter.	2 / 5
Actionability	Most rules provide concrete Don't/Do code examples (TypeScript wrapping, proprietary path stripping, code-search URL removal, Promise.all fan-out), though a few (T1-01 downstream verification, T5-01 pruning) stay abstract without commands, leaving minor gaps.	4 / 5
Workflow Clarity	The content is a per-rule reference rather than a sequenced workflow, and destructive/batch operations like dead-code elimination (T5-01) lack explicit validation or verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	Chapter sections and summary tables give reasonable in-file navigation, but the entire 530-line, seven-chapter guide is inlined in a single monolithic SKILL.md with no bundle files or one-level-deep references to split the content.	3 / 5
	Total	12 / 20 Passed

Description

48%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 names a clear, distinctive Gerrit niche and a broad set of sub-domains, but relies on a generic action verb ("Provides rules, patterns, and best practices") and omits any explicit "Use when" trigger guidance. It is recognizable but under-specified on both concrete actions and triggering conditions.

Suggestions

Replace the generic "Provides rules, patterns, and best practices" with concrete actions, e.g. "Enforces line-length formatting, strips proprietary paths from API docs, parallelizes client-side dashboard queries, and prunes decommissioned experiment fallbacks in Gerrit."

Add an explicit "Use when..." clause, e.g. "Use when working in the Gerrit codebase on frontend TypeScript formatting, release-note footers, downstream plugin releases, or visual regression test determinism."

Include natural trigger synonyms users would say (e.g., "Gerrit", "release notes", "Release-Notes footer", "screenshot tests", "dead-code cleanup") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The action "Provides rules, patterns, and best practices" is generic, and while multiple Gerrit sub-domains (hygiene, formatting, downstream plugin dependencies, release operations) are named, the described actions are minimal and abstract rather than concrete.	2 / 5
Completeness	A clear "what" is present (provides rules/patterns/best practices for the listed Gerrit domains), but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Gerrit" is a strong natural trigger and "code hygiene", "formatting", and "release operations" are relevant, but common variations/synonyms are missing and the phrasing is somewhat jargon-heavy ("downstream plugin dependencies").	3 / 5
Distinctiveness Conflict Risk	"Gerrit" plus the specific operations niche makes it mostly distinct with minimal conflict risk, though the broad "code hygiene, formatting" framing has minor overlap with general code-quality skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (539 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: GerritCodeReview/gerrit
Path: configs/skills/gerrit_hygiene_operations/SKILL.md
Commit: 49c7e7c

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