Loading...
Loading...
Found 179 Skills
Analyze existing repositories, maintain structure, setup guardrails and best practices
Format code on the current branch using Biome. Use when asked to format, lint, or clean up code before committing or creating a PR.
Linting workflows with neostandard and ESLint v9 flat config
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
Run Python quality checks with ruff, pytest, mypy, and bandit in deterministic order. Use WHEN user requests "quality gate", "lint", "verify code quality", "check python", or "pre-commit check". Use for pre-merge validation, CI/CD gating, or comprehensive code quality reports. Do NOT use for single-tool runs (run tool directly), debugging runtime bugs (use systematic-debugging), refactoring (use systematic-refactoring), or architecture review.
Verifies code changes by running tests and generation scripts
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.
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
Fix knip "Unused exports" violations. Handles all violation categories: test-only exports (extract to new file), dead barrel re-exports (remove from index.ts), and internally-only-used exports (un-export). Use when `npm run knip` reports unused exports.
Writing skill for Chinese technical documentation and product copy — enforces clarity, correct typography, and avoids buzzwords.
Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.