Loading...
Loading...
Found 183 Skills
Verifies code changes by running tests and generation scripts
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.
This skill should be used when users encounter cspell unknown word warnings, spelling errors from cspell diagnostics, or CI/linting failures on unrecognized words. Also applies when users ask to add words to the cspell dictionary, suppress or ignore cspell warnings, choose between cspell:words and cspell:ignore directives, or bootstrap cspell config in a new project
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
Analyze existing repositories, maintain structure, setup guardrails and best practices
Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.
Linting workflows with neostandard and ESLint v9 flat config
Format code on the current branch using Biome. Use when asked to format, lint, or clean up code before committing or creating a PR.
Run full validation to ensure code is ready for merge. Use before merging PRs, when asked to validate readiness, or as a final check before requesting review.
Define a precise React Doctor rule contract before implementation. Use when validating a rule idea, collecting official or open-source evidence, identifying false-positive traps, choosing detector precision, or setting first-version boundaries.
Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.