PHP Clean Naming Analyzer FAQs

Question 1

Does this skill follow standard PHP PSR guidelines?

Accepted Answer

Yes, it is designed to align with PSR naming conventions, recommending camelCase for variables and methods, PascalCase for classes, and UPPER_SNAKE_CASE for constants.

Question 2

How does it help with boolean logic?

Accepted Answer

The skill flags booleans that lack descriptive prefixes like 'is', 'has', or 'can', and warns against using negated names (like '$isNotValid') which can lead to confusing double negatives in code.

Question 3

What does the check-naming skill specifically look for?

Accepted Answer

It analyzes PHP code for four main issues: non-descriptive names (like single letters), unclear abbreviations, inconsistent casing (mixing snake_case and camelCase), and misleading names that don't match the actual behavior of the code.

Question 4

Is the output easy to act upon during a refactor?

Accepted Answer

The skill provides a structured output that includes the severity of the issue, the exact file location, the current code, a suggested replacement, and the rationale for the change.

Question 5

Can it help improve class and method architecture?

Accepted Answer

Yes, it identifies generic class names like 'Manager' or 'Helper' and suggests more specific alternatives, while also ensuring methods describe their actions and return types clearly.

PHP Clean Naming Analyzer

Key Features

Use Cases

PHP Clean Naming Analyzer

Key Features

Use Cases