Explorar skills

Use when reviewing a pull request, merge request, or local diff for correctness, security, and code quality.

Gerencia operações de fluxo de trabalho de PR, como criar, verificar status, vincular a issues, buscar comentários, abordar feedback, monitorar PRs e salvar notas. É acionada por comandos como 'pr create', 'pr checks' e 'watch pr'.

Use whenever a task requires an API key, token, password, or other credential. Checks the local tsm vault first; teaches safe retrieval patterns by tool category.

Recommends the right caching layer, TTL strategy, and invalidation approach for any application bottleneck.

Use when the user wants to plan a feature, design an implementation approach, or break down a complex task before coding.

Use when auditing and fixing error handling in a scope — swallowed exceptions, defaults returned on error, optional chaining masking missing data, floating promises / missing awaits, entry points with no error boundary, resource leaks on error paths. Triggers on "audit error handling", "hunt silent failures", "fix swallowed errors", "check error boundaries", "missing await".

Test framework router and infrastructure setup across multiple languages and platforms. Use when the user asks to choose a test framework, scaffold test infrastructure, add focused unit/integration/E2E/accessibility coverage, or integrate tests into CI/CD. Covers Rust, TypeScript/React, PHP/TYPO3, Shell, Playwright, accessibility, mutation, and fuzz testing as selectable modules. NOT for TDD metho

Code review via OpenCode — review uncommitted changes, branches, or commits

Identify what users actually need using functional/emotional/social jobs, needs-vs-wants laddering, latent-need surfacing, and job statements. Use when the user asks what users truly need, wants to write a job statement (When/I-want-to/So-I-can), wants to move past stated wants to underlying needs, needs to separate functional jobs from emotional or social ones, or wants to spot latent needs the u

Analyzes React components for performance, accessibility, and modern hook usage.

Use when the user wants to refactor, clean up, restructure, or reorganize existing code without changing behavior.

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".