triage▌

PRの変更内容を分析し、後続のコードレビューフェーズに必要な情報を構造化して出力するスキルです。 軽量モデル（Haiku）での実行を想定しており、CI環境でのコスト最適化に寄与します。

Deterministic WordPress repository inspection with structured JSON output for workflow guidance. \n \n Detects project kind (plugin, theme, block theme, WP core, Gutenberg, full site) and outputs a schema-validated JSON report including tooling, tests, and version hints \n Runs via Node.js detector script at repo root; outputs project.kind , signals , and tooling fields to guide downstream workflows \n Identifies PHP/Node tooling presence and test frameworks to inform which commands and conventi

Fetch, analyze, and summarize TestFlight crashes, beta feedback, and performance diagnostics via asc. \n \n Retrieves crash reports filtered by app, build, device model, or OS version; supports pagination and multiple output formats (JSON, table, markdown) \n Fetches beta tester feedback with optional screenshot inclusion and build-level filtering \n Analyzes performance diagnostics (hangs, disk writes, launch metrics) by signature and diagnostic type \n Resolves app and build IDs automatically;

Quickly summarize unread Gmail inbox messages with sender, subject, and date. \n \n Displays up to 20 unread messages by default; customize with --max flag \n Supports Gmail search queries via --query flag to filter beyond unread (e.g., from:boss ) \n Read-only operation; never modifies your mailbox \n Optional --labels flag includes label names in output; supports JSON format for scripting \n

Diagnose and resolve Fedora Linux issues with dnf, systemd, and SELinux guidance. \n \n Accepts optional Fedora release version and problem constraints to tailor troubleshooting scope \n Provides step-by-step triage plans using systemctl, journalctl, and dnf with copy-paste-ready commands \n Includes verification steps after each remediation and addresses SELinux and firewalld considerations \n Offers rollback and cleanup procedures to safely undo changes \n

Automated GitHub issue triage with real-time streaming analysis and background task parallelization. \n \n Launches one independent background task per issue for concurrent analysis, eliminating sequential bottlenecks \n Streams results in real-time as each task completes, providing immediate visibility into critical issues and recommended actions \n Categorizes issues by type (bug, feature, question, invalid) and status (resolved, needs action, can close, needs info) with priority flagging for

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user.