Explorar skills

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use quando o usuário quer saber o que será afetado por uma mudança ou precisa de análise de segurança antes de editar o código.

Fetches skills.sh trending rankings. Use when asking about skill rankings or popular tools.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Busca repositórios em alta por tópico no GitHub. Use ao perguntar sobre repositórios em alta do GitHub ou projetos de código aberto.

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"

Use when beads/Dolt database initialization fails, when bd commands return errors about missing databases, when setting up beads in a new project, or when recovering from diverged Dolt history. Handles fresh init, bootstrap from remote, and recovery workflows.

Use when implementing any feature or bugfix, before writing implementation code

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation