Desenvolvimento

Debug issues through structured investigation, failing test creation, and targeted fixes. Use when the user provides an error message, traceback, steps-to-reproduce, or describes unexpected behavior.

Dynamic Expert Council QA system. Selects domain-relevant expert personas to review deliverables before final delivery. 3 tiers with build/review mode toggle. Works with any AI assistant.

Audit the latest GitHub Actions workflow runs on the current branch/PR for warnings, errors, failures, deprecation notices, and other log noise — then fix what's fixable in-repo (workflow YAML, configs, source, tests). Hands commit + push back to the developer. Use after CI finishes and before merge, or whenever the user asks about failing/noisy CI — phrasings like "audit the PR", "why did CI fail

Performs comprehensive codebase audit checking architecture, tech debt, security vulnerabilities, test coverage, documentation, dependencies, and maintainability. Use when auditing a project, assessing codebase health, running security scans, checking for vulnerabilities, reviewing code quality, analyzing tech debt, or asked to audit/analyze the entire codebase.

Externalize a project that has become a hairball into a visible map plus one concrete next action. Use when the user says they are "overwhelmed", "lost", "stuck", "drowning", "buried", "spinning", "don't know where to start", "can't see the shape", "too many pieces/things/tabs", "spending too many cycles", or asks to "map this project" / "zoom out" / "what's next". Sub-actions: map (default), next

Claude Code Skills

Invoke for any request to create, file, open, or record a new GitHub issue. Trigger on:\n- Direct creation: 「issue 作って」「起票して」「issue 立て(といて)」「issue 化して」「issue 作れる?」\n- Record intent: 「issue に残したい/残しておいてほしい」「issue として残しておきたい」\n- Issue types: bug reports (with repro steps), feature requests, refactoring tasks, doc fixes, code-review findings to track later\n\nDo NOT trigger for viewing, listing, sear

Pacote de habilidades JUnit 5 para criar, depurar, modernizar, documentar e rotear fluxos de trabalho de teste JVM.

Claude Code 専用。素の `claude` で起動した直後に、タスク説明または issue URL / 番号から命名した git worktree へ `EnterWorktree` で切り替えて作業を開始する。issue 起点・タスク起点どちらでも並列セッション立ち上げに使う。issue URL / 番号入力で Status: Ready の場合は worktree 切り替え後に `issue-implement` へ自動連鎖する。

契約書・利用規約を読み込み、リスク条項・不利な条件・確認すべき点を一覧化するスキル。法的アドバイスではなくチェックリストとして使用する。

Ask clarifying questions in rounds until the task is unambiguous, before producing any code, research, or other output. Manually invoked only via slash command. Useful when the cost of getting the work wrong is higher than the cost of a few extra messages. Applies to coding, research, design, writing, refactoring, and analysis.

Use when refactoring AI-generated code projects (vibe-coded apps, Claude/Cursor/GPT output) that have visual inconsistency, code duplication, lack of design system, or structural problems. Trigger on "refactor this AI project", "fix the design", "clean up this vibe-coded app", or when inheriting an AI-generated codebase.