kevinslin/llm

Overview

This skill runs linting and formatting workflows for a JavaScript project and reports status. It executes the project's lint and format npm scripts, attempts automated fixes when possible, and returns a clear success or failure result. The goal is to ensure code quality checks pass before commits or CI runs.

How this skill works

The skill runs npm run lint followed by npm run format in the project root. If lint reports errors that can be auto-fixed, the skill applies fixes, reruns lint, and verifies the errors are resolved. If both commands complete without error it prints "success"; otherwise it surfaces remaining issues and suggests remediation steps.

When to use it

• Before committing or opening a pull request to ensure code style and lint rules pass
• As a pre-merge CI step to enforce consistent formatting and catch static issues early
• During local development to automatically apply formatter rules and reduce manual fixes
• When onboarding a new contributor to validate their environment runs the same checks

Best practices

• Ensure npm scripts lint and format are defined and configured in package.json
• Run the skill from the project root where node modules and config files (ESLint, Prettier) are present
• Commit configuration files (.eslintrc, .prettierrc, etc.) so lint/format behave consistently across environments
• If lint errors persist after auto-fixing, open the reported files and fix logic issues manually, then re-run lint
• Keep devDependencies for ESLint and formatters up to date to avoid rule mismatches

Example use cases

• Pre-commit hook integration that calls the skill to auto-fix formatting and fail commits if lint errors remain
• CI pipeline step that enforces code quality by running the skill and rejecting builds on failure
• Local developer workflow: run the skill to auto-format code and catch eslint rule violations before pushing
• Automated PR bot that runs the skill and posts results or fixes to the pull request comments