hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

Quality

83%

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

78%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 compact, actionable skill body with concrete commands and a well-organized structure appropriate for a single-purpose skill. The main gap is the absence of an explicit error-recovery loop when the hygiene check fails.

Suggestions

Add a short feedback loop, e.g. 'If hygiene fails, fix the reported issues and re-run `npm run precommit` before declaring work complete.'

Include the exact Microsoft copyright header text (or a pointer to it) so the copyright-header check is fully actionable.

Trim the redundant sentence 'This catches issues that would block a commit.' since the 'before declaring work complete' instruction already conveys it.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with executable commands and a tight rule list; the line 'This catches issues that would block a commit' is mildly redundant with the 'before declaring work complete' instruction.	4 / 5
Actionability	It gives concrete, copy-paste-ready commands ('npm run precommit', 'node --experimental-strip-types build/hygiene.ts path/to/file.ts') and specific suppression comments, though the expected copyright header text is not provided.	4 / 5
Workflow Clarity	The single-step workflow is unambiguous ('Always run the pre-commit hygiene check before declaring work complete') and the rule list tells Claude what to fix, but there is no explicit fix→re-run feedback loop for failures.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (none exist), and is organized into clear 'Running the hygiene check' and 'What it checks' sections, meeting the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

88%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 strong, concrete description with an explicit 'Use when' trigger and a comprehensive list of what it covers. The only soft spot is the broad 'making code changes' trigger, which slightly raises overlap risk with general linting skills.

Suggestions

Tighten the trigger to a more specific phrase (e.g. 'Use before committing code changes in the VS Code repo') to reduce overlap with generic linting skills.

Add one common synonym a user might say, such as 'lint' or 'style checks', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete checks — 'pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint' — giving comprehensive coverage of the hygiene domain rather than vague language.	5 / 5
Completeness	It explicitly answers both what (the listed hygiene checks) and when ('Use when making code changes to ensure they pass VS Code's hygiene checks') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Natural phrases like 'making code changes', 'hygiene checks', and 'pre-commit hook' appear, but a few common variations users might say (e.g. 'lint', 'commit', 'style checks') are not present.	4 / 5
Distinctiveness Conflict Risk	'VS Code's hygiene checks' carves a clear niche with distinct triggers, but the broad 'making code changes' condition could overlap with general code-quality or linting skills.	4 / 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: posit-dev/positron
Path: .github/skills/hygiene/SKILL.md
Commit: 9bb0f27

Reviewed: about 21 hours 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.