Configure and run Ultracite linting and formatting for JavaScript and TypeScript projects.
npx skills add https://github.com/yehezkieldio/topaz --skill ultracite-yehezkieldio
Please help me install this Agent Skill. Skill: ultracite Source: https://github.com/yehezkieldio/topaz/tree/main/.agents/skills/ultracite Command: npx skills add https://github.com/yehezkieldio/topaz --skill ultracite-yehezkieldio
ultracite init interactively or with non-interactive flags for package manager, linter backend, editors, AI agents, frameworks, and git hooks. - Linting and Formatting Commands: Execute check, fix, and doctor commands with file path arguments and pass-through options to the underlying linter. - Code Standards Reference: Apply Ultracite's rules for type safety, async correctness, React accessibility, security, and performance when writing or reviewing code. - Use Case: A developer joins a Next.js project using Ultracite with Biome. The Skill helps detect the active linter from biome.jsonc, run bunx ultracite fix before committing, and follow the preset's accessibility and type-safety rules when writing new components. ## Quick Start Ask the assistant to check this project for linting issues with Ultracite and automatically fix any problems it finds.High-intent search queries and answers about installing and using this skill.
Run bunx ultracite init for interactive setup, or pass flags like --pm bun, --linter biome, --frameworks react next, and --quiet for non-interactive CI use. Init creates a config file extending Ultracite presets and can install dependencies automatically.
Use bunx ultracite check to report issues read-only and bunx ultracite fix to auto-fix them. Both accept optional file paths, and unknown options pass through to the underlying linter, such as --max-warnings 0.
Biome is the recommended backend and the default suggestion in Ultracite. ESLint pairs with Prettier and Stylelint for teams needing the ESLint ecosystem, while Oxlint with Oxfmt offers a Rust-based alternative with type-aware linting via oxlint-tsgolint.
Detection searches upward from the current directory for config files: biome.json or biome.jsonc indicates Biome, eslint.config files indicate ESLint, and oxlint.config.ts indicates Oxlint. It also checks that ultracite appears in package.json dependencies.
Rules fail to apply when the config file does not extend the correct Ultracite presets for your framework, or when legacy configs like .eslintrc or .prettierrc conflict. Run bunx ultracite doctor to diagnose installation, config validity, and conflicting tools.
Yes, pass the --quiet flag or set CI=true to suppress prompts, combined with explicit flags for package manager, linter, editors, agents, frameworks, and integrations. Use --skip-install to skip dependency installation when the environment already has them.
tuliofStandardizes linting and formatting for JavaScript and TypeScript projects via a unified preset.
Coverage-CreativesAutomate code quality checks with Git hooks, lint-staged, Husky, and Commitlint.
dotBeepsRun tsc and ESLint to detect, interpret, and prioritize TypeScript errors.
camoneartAutomate NextJS project setup with ESLint, Prettier, and Tailwind CSS configuration.