lint-fix
Fix violations of an eslintPluginScraps rule across the codebase. Use when asked to "fix lint violations", "apply a lint rule", "fix scraps rule errors", "roll out a lint rule", "enforce a rule codebase-wide", or "fix design system lint". Covers manual fixes, autofix, batching, and codemod strategies for large-scale rollouts.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (fixing eslintPluginScraps rule violations), provides explicit trigger phrases via a 'Use when...' clause, and lists specific strategies (manual fixes, autofix, batching, codemod). It is well-differentiated from generic linting or code quality skills due to the specific plugin and rollout focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: fix violations of an eslintPluginScraps rule, manual fixes, autofix, batching, and codemod strategies for large-scale rollouts. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (fix violations of eslintPluginScraps rules using manual fixes, autofix, batching, codemod strategies) and 'when' (explicit 'Use when...' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger phrases users would actually say: 'fix lint violations', 'apply a lint rule', 'fix scraps rule errors', 'roll out a lint rule', 'enforce a rule codebase-wide', 'fix design system lint'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to eslintPluginScraps rule violations and large-scale lint rollouts. The combination of the specific plugin name and the codebase-wide rollout focus creates a clear niche unlikely to conflict with general linting or code formatting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently guides Claude through fixing lint violations at any scale. It excels at providing concrete commands, clear decision points based on violation count, and a well-structured workflow with validation checkpoints. The progressive disclosure to reference files for per-rule fix details is well-organized and clearly signaled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what ESLint is, what codemods are, and how to work with globs. Every section earns its place with no unnecessary explanations of basic concepts. The table format for rule references is particularly token-efficient. | 3 / 3 |
Actionability | Every step includes concrete, copy-paste-ready bash commands with proper argument substitution. The strategy selection is based on specific violation count thresholds, and the fix workflow provides an explicit tight loop. PR title conventions and pre-commit commands are fully specified. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: understand → assess scale → choose strategy → fix loop → coordinate → verify. Each strategy tier has explicit steps with validation checkpoints (re-run after each batch, verify with tail command, final verification step). The tight loop includes a feedback cycle of fix → re-run → expand scope. | 3 / 3 |
Progressive Disclosure | The SKILL.md serves as a clear overview with well-signaled one-level-deep references to fix-patterns.md and token-taxonomy.md. The table clearly maps each rule to its reference file. Content is appropriately split between the overview workflow here and detailed fix patterns in referenced files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- getsentry/sentry
- Commit
552fb5c
- Reviewed
Table of Contents
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.