Loading...
Loading...
Found 65 Skills
Lists available make commands for Streamlit development. Use for build, test, lint, or format tasks.
TypeScript code style guide and formatting conventions. Use when writing TypeScript code, reviewing TypeScript files, refactoring .ts code, formatting TypeScript, or when working with TypeScript interfaces, classes, functions, or any .ts files. Apply these rules during code generation, code review, and when user mentions TypeScript style, formatting, conventions, semicolons, or code quality.
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint)
Implement static code analysis with linters, formatters, and security scanners to catch bugs early. Use when enforcing code standards, detecting security vulnerabilities, or automating code review.
Build, tune, and operate Ruff for Python linting, formatting, and editor/CI integration. Use when adding or updating Ruff configuration, migrating from Black/Flake8/isort, selecting rule families, enforcing fix safety, or debugging lint/format behavior in local development, pre-commit, and CI.
Enforce Pythonic standards using Black, Isort, and Flake8. Use to ensure consistency across large Python codebases and team environments.
Check code quality and formatting before committing changes
Galaxy code linting, formatting, and type checking. Run checks, auto-fix formatting, Python lint, client lint, mypy type checks. Use for: ruff, flake8, black, isort, darker, autoflake, pyupgrade, eslint, prettier, mypy, tox, make format, make diff-format, code style, lint failures, CI lint checks, formatting errors, type errors, codespell, redocly, api schema, xsd, config lint.
Configuring @nuxt/eslint-config for framework support, formatters, and rule overrides. Use when adding Vue/Nuxt/Typescript support, customizing rules, or setting up editors integration.
This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
Standards for code linting, formatting, and pre-commit hooks.