The description does not list any concrete actions (e.g., 'run linter', 'auto-fix formatting', 'check style rules'). It only references situations ('lint errors', 'formatting issues') without specifying what the skill actually does.

The description answers 'when' fairly well with explicit trigger conditions, but completely fails to answer 'what does this do'—there is no explanation of the skill's capabilities or actions. The 'what' is entirely missing.

Includes some natural keywords like 'lint errors', 'formatting issues', 'committing code', and 'CI', which users might naturally mention. However, it misses common variations like 'eslint', 'prettier', 'code style', 'linting', 'format code', or specific tool names.

The mention of 'lint errors', 'formatting issues', and 'CI' provides some specificity, but without naming concrete tools or actions, it could overlap with general code quality, testing, or CI/CD skills.

Very lean and efficient. No unnecessary explanations of what linting or formatting are. Every line serves a purpose. The common mistakes section adds genuine value without padding.

Provides specific commands (`yarn prettier`, `yarn linc`) which is good, but lacks guidance on what to do when lint errors are found (step 3 is vague: 'report any remaining manual fixes needed'). No examples of common lint errors or how to fix them.

Steps are clearly sequenced, but there's no validation/feedback loop — e.g., after fixing lint issues, should you re-run `yarn linc` to confirm? There's no explicit checkpoint confirming all issues are resolved before committing.

For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Instructions and Common Mistakes). No bundle files are needed.