Explorar skills

Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradations. Compares HEAD → working tree by default. Walks the full reachable file set from SKILL.md via mark

Uma skill de segurança Go para revisão de código.

Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

An example skill for testing diff-skill evaluation.

Uma skill de teste

Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.

Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.

Aplique o prompting Chain-of-Verification (CoVe) para melhorar a precisão das respostas através da auto-verificação. Utilize-o quando perguntas complexas exigirem verificação de fatos, precisão técnica ou raciocínio em múltiplas etapas.

TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.

Reviews tool configurations for correctness.

After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.