JS/TS Code Quality FAQs

Question 1

Which file extensions are supported by this skill?

Accepted Answer

The skill supports all common JavaScript and TypeScript extensions, including .js, .jsx, .ts, .tsx, .mjs, and .cjs.

Question 2

Do I need to manually run the linting commands?

Accepted Answer

The skill includes an automatic hook behavior that triggers after write and edit operations, though you can also run the underlying linting scripts manually via the CLI.

Question 3

How does the skill handle conflicts between ESLint and Prettier?

Accepted Answer

It follows industry best practices by prioritizing code quality rules in ESLint and formatting rules in Prettier, often utilizing tools like eslint-config-prettier to prevent rule collisions.

Question 4

Does this skill replace my existing ESLint configuration?

Accepted Answer

No, the skill follows a 'project config wins' philosophy. If your project has an existing ESLint or Prettier configuration, the skill will detect and respect those settings rather than overriding them.

Question 5

What is the benefit of using Biome over ESLint?

Accepted Answer

Biome is a Rust-based unified toolchain that is often 10-100x faster than ESLint. It handles both linting and formatting in a single pass, making it ideal for large codebases where performance is critical.

JS/TS Code Quality

주요 기능

사용 사례

JS/TS Code Quality

주요 기능

사용 사례