What problem does it solve? Codebases accumulate inconsistent boolean naming (bare flags like stop, negative names like isNotValid, single-letter parameters like v bool), deeply nested conditionals, and non-standard enum declarations that hurt readability and maintainability. Manually auditing every file against coding guidelines is slow and error-prone. ## Core Features & Use Cases - Boolean Convention Enforcement: Detects and rewrites violations such as == true comparisons, negative identifiers (isNotValid, hasNoData), unprefixed flags (dryRun, force), and inverted empty checks (!isEmpty -> isDefined). - Conditional Flattening: Eliminates nested if blocks and compound negative chains using guard clauses, early returns, and pre-evaluated single-variable boolean checks. - Enum Standardization: Enforces the Type suffix on all enum declarations across TypeScript, Go, and PHP. - Use Case: A team maintaining a large Go monorepo runs this Skill to sweep every source file, rename SetStopOnFail(v bool) to SetStopOnFail(isStopOnFail bool), flatten nested conditionals, and validate results with the bundled linter before a single atomic commit. ## Quick Start Ask the agent to audit the repository for boolean naming violations and nested if statements, then refactor all offending files to follow the coding guidelines and commit the changes.
