Explorar skills

Use before writing any code for a new feature, task, or significant change — produces a structured implementation plan with affected files, ordered steps, risks, and open questions. Always invoke this at the start of any non-trivial implementation task and wait for explicit approval before writing code.

Use when you are about to open a GitHub pull request — generates a semver-prefixed title ([PATCH/MINOR/MAJOR] TICKET: description) and structured body from commits. Always invoke this instead of running gh pr create directly.

Score and prioritize all open GitHub Issues by Impact x Effort x Urgency. Outputs a triage matrix (TRIAGE.md), applies priority labels, and suggests a sprint plan. Use when your issue backlog is overwhelming, you don''t know what to work on next, or you want a structured sprint plan. Triggers on: "issue 整理", "バックログ整理", "何から手をつける", "issue優先度", "sprint plan", "issue-triage", "issue triage". DO NOT U

Use when you need to investigate an unfamiliar library, framework, architectural question, or technical decision — spawns the researcher agent which explores the codebase and searches external sources in parallel. Invoke before making technology choices or when the right approach is unclear.

Use before committing or opening a pull request — reviews staged changes as a principal engineer for correctness, edge cases, and logic flaws. Always invoke this before creating a PR.

Use when you want a dedicated security review of staged or recently changed files — deeper than the security section in /review. Covers OWASP Top 10, secrets exposure, dependency vulnerabilities, and auth gaps. Run before opening a PR on security-sensitive changes.

Use before implementing a complex, high-stakes, or cross-cutting feature — produces a full technical specification including data model, API contract, edge cases, and open questions. The planning layer above /plan. Invoke this when /plan alone isn't detailed enough.

Use when you want to surface accumulated technical debt — scans for TODOs, deprecated APIs, dead code, and code quality issues. Produces a prioritized list with age and estimated effort. Run periodically or before planning a refactor sprint.

Use when you need to document E2E test cases for a feature or bug fix that can't be covered by unit or integration tests alone. Auto-detects ticket from branch name. Reuses codebase context from /plan if already run; falls back to git diff + explorer when invoked standalone. Outputs to a markdown file by default.

Address open GitHub PR review comments automatically. For each unresolved comment, classifies as MUST-FIX (edit code), ACK (reply only), or DISCUSS (ask back). Edits the relevant files, commits, and drafts a response comment for each item. Use when you receive PR review feedback and want to address all comments in one pass. Triggers on: "PRのコメントに対応", "review comments", "address PR feedback", "レビュー

Generate human-readable release notes from git history and merged PRs. Creates two versions: user-facing (what''s new in plain language) and developer-facing (conventional changelog format). Publishes as a GitHub Release draft with auto-suggested semver bump. Use when you''re preparing a release, want to document what changed since the last tag, or need to write CHANGELOG entries. Triggers on: "リリ

Generate a comprehensive onboarding guide for any codebase. Produces a REPO_TOUR.md with a 30-second summary, annotated directory tree, Mermaid architecture diagram, key files list, and "where to look for X" quick-reference. Use when you''re new to a codebase, onboarding a team member, or need to document the overall structure. Also useful after a major refactor to update understanding. Triggers o