Desenvolvimento
13.569 skills encontradas
Alerta por categoria
Receba novas skills de Desenvolvimento toda segunda
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
codex-review
Code review via OpenAI Codex — review uncommitted changes, branches, or commits
ml-model-eval-benchmark
Compare model candidates using weighted metrics and deterministic ranking outputs. Use for benchmark leaderboards and model promotion decisions.
legacy-rescue
Loop workflow for making real progress on a legacy codebase without breaking production. Starts by generating a codemap so you actually understand what exists (documentation-generator), identifies feedback-center modules (systems-thinking), gets a second perspective on areas you'll touch (code-review), builds a test safety net before any changes (test-driven-development), plans changes with rollba
audit-structure
Use when auditing repo topology in a scope — code grouped by type where the repo groups by feature, god-modules, misplaced files, leaky or missing module boundaries, layer-direction violations, import cycles, over-nesting. Triggers on "audit structure", "repo structure review", "fix module boundaries", "check layering", "files in the wrong place".
hwp-template
한글 서식을 템플릿으로 저장/관리합니다. "템플릿 저장", "서식 등록", "템플릿 목록" 요청시 사용합니다.
pentest-lateral-movement
Assess lateral movement and pivot paths across authorized internal trust boundaries.
pr-review
Use when reviewing a pull request, merge request, or local diff for correctness, security, and code quality.
plan
Use when the user wants to plan a feature, design an implementation approach, or break down a complex task before coding.
opencode-review
Code review via OpenCode — review uncommitted changes, branches, or commits
refactor
Use when the user wants to refactor, clean up, restructure, or reorganize existing code without changing behavior.
audit-correctness
Use when auditing and fixing logic bugs in a scope — off-by-one, wrong operator, inverted condition, unhandled boundary cases, unit/dimension mismatch, code that doesn't do what its name or docstring claims. Triggers on "audit correctness", "fix logic bugs", "check for off-by-one", "correctness review".
audit-necessity
Use when cutting code in a folder that doesn't earn its keep — whether a solution is over-engineered, where maintenance cost can be reduced, or where a feature should be removed entirely.