Total 54,172 skills, Code Quality has 2444 skills
Showing 12 of 2444 skills
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
Você é uma Arquiteta de Software Sênior especialista em Clean Code e engenharia de software. Use esta skill sempre que o usuário pedir para revisar, criticar, refatorar ou avaliar trechos de código, funções, classes, módulos ou arquiteturas inteiras. Ative também quando o usuário mencionar problemas como "código duplicado", "classe muito grande", "difícil de manter", "código espaguete", "muita dependência", "quero melhorar esse código", "está violando SOLID?", "como refatorar isso?", "esse código está limpo?", "tem code smell aqui?", "como aplicar injeção de dependência?", "preciso de um code review", ou qualquer variação dessas frases. Ative inclusive quando o usuário perguntar sobre boas práticas de design, padrões de código, ou pedir explicações sobre KISS, DRY, YAGNI, TDA, SOLID e seus subprincípios. Se estiver no SynkOS, chame `pane_set_identity` com skill="clean-code-architect" e role="architect".
Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.
Performance profiling and optimization for Roblox. Server frame time, client FPS, memory management, network bandwidth, Luau-specific optimization, asset budgets. Use when diagnosing lag, optimizing hot paths, or setting performance budgets.
Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Active coding loop — feature stages (brainstorm→plan→interface→tests→implement→improve→review→loop), red-green TDD execution, build-fix, deps-check, coding standards, bug-fix learning. Owns the canonical testing doctrine. Use when writing or changing code (backend, logic, APIs, libraries, CLIs).
AFK adversarial code-review loop: Cursor agent CLI critic (grug + thermo-nuclear) produces structured findings; Codex validator confirms or pushbacks on regression risk; parent adjudicates and commits fixes per finding until clean. Config at ~/.config/adversarial-review/config.toml. Use for adversarial review, clean code loop, or unattended branch hardening.
Findings-first review discipline for code, diffs, task plans, live workflow changes, and implementation evidence.
Verify code against paper. Use when user asks "does this match the paper", "check my implementation", or is implementing equations/algorithms from literature.
Systematically find blind spots in code, architecture, APIs, and deployment — structured critique that catches what familiarity hides