Total 30,737 skills, Code Quality has 1622 skills
Showing 12 of 1622 skills
Guide for creating high-quality, user-friendly diagnostics in Biome. Use when implementing error messages, warnings, and code frame displays. Examples:<example>User needs to create a diagnostic for a lint rule</example><example>User wants to add helpful advice to error messages</example><example>User is improving diagnostic quality</example>
Step-by-step guide for creating and implementing lint rules in Biome's analyzer. Use when implementing rules like noVar, useConst, or any custom lint/assist rule. Examples:<example>User wants to create a rule that detects unused variables</example><example>User needs to add code actions to fix diagnostic issues</example><example>User is implementing semantic analysis for binding references</example>
Guide for working with Biome's module graph and type inference system. Use when implementing type-aware lint rules or working on TypeScript support. Examples:<example>User needs to understand type resolution for a lint rule</example><example>User is working on the module graph infrastructure</example><example>User wants to implement type inference for a new feature</example>
Implement FireCrawl lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for FireCrawl integrations, implementing pre-commit hooks, or configuring CI policy checks for FireCrawl best practices. Trigger with phrases like "firecrawl policy", "firecrawl lint", "firecrawl guardrails", "firecrawl best practices check", "firecrawl eslint".
Implement Exa lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Exa integrations, implementing pre-commit hooks, or configuring CI policy checks for Exa best practices. Trigger with phrases like "exa policy", "exa lint", "exa guardrails", "exa best practices check", "exa eslint".
Request code review and route results to a tmux pane. Default flow commits first; optional opt-in flow can target an existing commit without commit/push.
Run code-simplifier on current branch/PR changes to show a cleaned-up version
FaasJS best practices - file conventions, defineFunc, database(knex).
Review Vendure entities for missing VendureEntity inheritance, improper decorators, missing migrations, index violations, and TypeORM anti-patterns. Use when reviewing entity PRs or auditing data models.
Guides file and folder organization using fractal tree structure: self-similar directories, encapsulation, shared/ folders, mini-library pattern, and kebab-case naming. Use when creating, moving, or renaming files, extracting modules into subdirectories, deciding where shared code belongs, or checking import boundaries.
Automated code review loop with progressive reasoning levels. Runs n parallel Codex reviews (configurable via -n), Claude addresses issues, climbs from low→xhigh reasoning until fixed point (all n clean). Human approval at each iteration.
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.