Configure ESLint, Prettier, and Stylelint for automated code quality enforcement with pre-commit hooks and CI integration. [EXPLICIT] Trigger: "ESLint", "Prettier", "linting", "code formatting", "Stylelint"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.htmlSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
"Arguing about code style in reviews is a waste of time — let the machines decide." — Unknown
Guides the setup of automated code quality tools — ESLint for code correctness, Prettier for formatting, Stylelint for CSS, pre-commit hooks with Husky/lint-staged, and CI integration. Use when establishing or improving code quality tooling for a project. [EXPLICIT]
package.json for installed lint/format dependencies.prettierrc configpackage.json.editorconfig for cross-IDE consistencycode-review — linting removes style debates from code reviewsgithub-actions-ci — lint step in CI pipelineExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |