Code Quality Auditor FAQs

Question 1

What complexity metrics does the auditor track?

Accepted Answer

It tracks cyclomatic complexity (decision points), nesting depth (threshold of 4+ levels), method length (50+ lines), and file size (500+ lines for classes/modules).

Question 2

Does this skill automatically fix my code?

Accepted Answer

No, the Code Quality Auditor is a reporting worker. It identifies issues, calculates a compliance score, and provides recommendations, but it does not modify your source code to ensure you maintain architectural control.

Question 3

How does it detect N+1 query patterns?

Accepted Answer

The skill scans for database query patterns and ORM calls located inside loops (forEach, map, for/while), which are common indicators of performance-draining N+1 query issues.

Question 4

Can I scan specific parts of my project instead of the whole repository?

Accepted Answer

Yes, the skill supports a domain-aware mode. When provided with a specific domain path, it restricts its analysis to that directory, making it ideal for large monorepos.

Question 5

Which programming languages are supported?

Accepted Answer

The auditor is tech-stack aware and utilizes common tools like ESLint, Radon (Python), and Gocyclo (Go) alongside advanced Grep patterns to audit various languages.

Code Quality Auditor

주요 기능

사용 사례

Code Quality Auditor

주요 기능

사용 사례