Explorar skills

MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

Um fluxo de trabalho no GitHub, guiado por rótulos, que permite a uma IA local gerenciar issues e PRs, com um daemon despachando o trabalho. Todo o conteúdo relacionado a uma issue, incluindo propostas, código e conversas, é arquivado sob seu número para fácil recuperação e retomada. Os comandos incluem setup e status.

MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code

Evaluate and maximize GitHub repo quality from 7/10 to 10/10 perfect

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides

Create professional visual assets for GitHub repositories — architecture diagrams, social cards, and README banners.

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue

HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met

Recommend GitHub agent workflows (gh-aw) tailored to this repo. Use when the user asks which automations to add to their repo, what agentic workflows would help, or types /discover-workflows.

Compiles key events into a structured, scannable timeline — formatted as a table or numbered list — designed for use in graphic production, digital interactives, sidebar fact boxes, and editorial planning documents.

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks