Code Standards Detective FAQs

Question 1

How does this skill detect patterns in my code?

Accepted Answer

It uses a multi-phase approach: first parsing configuration files like .eslintrc and tsconfig.json, then performing statistical analysis on the actual source code using grep and glob tools to verify if those patterns are followed.

Question 2

What kind of anti-patterns can it find?

Accepted Answer

It identifies common issues such as improper error handling, excessive parameter counts, inconsistent naming, usage of restricted types (like 'any'), and forgotten debugging statements.

Question 3

Is the analysis based on my specific project or generic rules?

Accepted Answer

It is entirely evidence-based. Rather than applying generic rules, it looks at how you actually write code to determine what the project's 'real' standards are.

Question 4

Does it support languages other than TypeScript?

Accepted Answer

While it has specialized parsers for TypeScript and JavaScript configs, its core pattern detection logic uses universal tools like Grep, making it highly effective for most programming languages.

Question 5

Can it generate a formal style guide?

Accepted Answer

Yes, its primary output is a detailed Markdown report that documents naming conventions, import patterns, and function characteristics backed by real-world examples from your repository.

Code Standards Detective

About

Key Features

Use Cases

Code Standards Detective

About

Key Features

Use Cases