Detect and prevent UI/UX, code quality, N+1, and unsafe SQL anti-patterns.
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill anti-pattern
Please help me install this Agent Skill. Skill: anti-pattern Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/anti-pattern Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill anti-pattern
This skill helps you prevent unfinished, low-quality, and fragile code from being shipped by detecting common anti-patterns that make software look unprofessional or not production-ready.
Use case example: During a code review for a web feature, run this skill to ensure every button and form works, data is loaded from real sources (with loading/error states), and database access avoids N+1 query patterns.
Use the anti-pattern skill to scan the project and report any banned UX, code, N+1, or SQL anti-patterns that should be fixed before merging.
High-intent search queries and answers about installing and using this skill.
To detect N+1 queries and unsafe SQL patterns during code review, scan the codebase to identify loop-query execution, injection-prone string concatenation, and SELECT * constructs. This enforces parameterized, index-friendly SQL structures before merging.
Common UI UX anti-patterns include placeholder elements, non-functional buttons, hardcoded fake data, and missing loading or error states. Flagging these broken interaction patterns ensures web features load from real data sources and behave like production software.
Prevent technical debt and dead-code patterns before merging by scanning for unfinished, low-quality code behaviors. Code quality guardrails validate required handlers, enforce banned patterns, and detect fragile code smells for refactoring planning.
Yes, you can use automated checks to validate required behaviors, ensuring handlers and real data sources exist in your application. This verifies that all forms and buttons work and data is loaded properly without relying on hardcoded fake data.
The best way to enforce SQL best practices in web application codebases is to flag anti-pattern SQL constructs during pre-merge verification. This identifies injection-prone string concatenation and SELECT * usage, promoting safer query structures.
anishi1222Detect SQL injection vulnerabilities from string concatenation and unparameterized queries.
Jorge-IvanAnalyze code diffs and files for bugs, security vulnerabilities, and code smells.
zajcaConfigure golangci-lint with recommended Go linters for static analysis.
mthinesAnalyze test suites to verify imports and exercise of production functions.
