Evaluate code against 17 design smells and classify findings.
npx skills add https://github.com/codybrom/clairvoyance --skill red-flags-codybrom
Please help me install this Agent Skill. Skill: red-flags Source: https://github.com/codybrom/clairvoyance/tree/main/skills/red-flags Command: npx skills add https://github.com/codybrom/clairvoyance --skill red-flags-codybrom
This Skill helps identify software design problems that make code difficult to understand, change, or maintain before they become larger architectural issues.
Ask the red-flags skill to scan the specified file or directory and produce a prioritized diagnostic report with locations, violated principles, and recommended fixes.
High-intent search queries and answers about installing and using this skill.
To identify design smells before they become technical debt, scan code against 17 structural, boundary, and abstraction red flags. This diagnostic process classifies findings as CLEAR or TRIGGERED and maps related issues to architectural syndromes like shallow wrappers or leaky abstractions.
The best way to review a pull request for software architecture issues is to evaluate changes against a checklist of 17 design smells. This reveals hidden coupling, vague abstractions, and tactical shortcuts, providing prioritized corrective actions.
Detecting related red flags helps diagnose leaky abstractions by clustering individual findings into architectural syndromes. This pattern recognition connects isolated design smells, revealing broader structural issues like error avalanches or shallow wrapper stacks.
Yes, you can assess unfamiliar modules for hidden coupling by applying a comprehensive design scan. This evaluates code against 17 structural and boundary red flags, classifying each as CLEAR, TRIGGERED, or N/A to expose excessive interface complexity.
When a module assessment reveals error handling design smells, use the diagnostic report to map findings to specific design principles. This provides prioritized corrective actions to resolve detected architectural syndromes.
zcaceresIdentify untested branches, error paths, and boundary conditions in test suites.
aquariuscookApply behavior-preserving refactoring patterns to address code smells.
aniruddh2003Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.
brabos-aiValidate code against architectural contracts, IoC, RESTful, OWASP, SOLID, and quality metrics.
