Loading...
Loading...
Found 57 Skills
Load when working with contents in *.mo files
Merge-friendly import formatting (one-per-line, alphabetical). Auto-loads when writing TypeScript/JavaScript imports to minimize merge conflicts in parallel development. Enforces consistent grouping and sorting.
Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting.
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.
Open a pull request for the current feature
Configure Prettier for code formatting and TypeScript for typechecking. Includes VSCode settings and EditorConfig for consistent code style. Skips ESLint/Biome to avoid config complexity.
Run targeted linting, formatting, and code quality checks on modified files. Use this to validate code style, type safety, security, and other quality metrics before committing. Supports running all checks or targeting specific checks on specific files for efficient validation.
Next Friday code style rules for formatting, structure, and readability. Use when writing functions, conditionals, or organizing code.
Check code quality and formatting before committing changes
Configure and operate BiomeJS in JavaScript/TypeScript projects, including installation, `biome.json` setup, formatter/linter/check workflows, VCS integration, and CI usage. Use when users ask to adopt Biome, tune rules/includes, set up monorepo/shared configs, or troubleshoot Biome command behavior.
QLTY During Development
Standards for code linting, formatting, and pre-commit hooks.