2,300 件 ・ 関連度順
概要と使いどころ
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Azure incidents and service degradations with a read-only workflow using Azure CLI, Resource Health, Activity Log, metrics, resource logs, and official Microsoft docs. Use when troubleshooting Azure outages, Resource Health alerts, Azure Firewall or DNS failures, ExpressRoute or BGP instability, VM availability problems, AKS incidents, App Service failures, database connectivity issues, Entra ID sign-in problems, load balancer issues, platform-vs-workload cutover, or drafting a troubleshooting report. Triggers on 'Azure トラブルシューティング', '障害調査', '切り分け', 'Resource Health', '復旧確認', 'Azure Firewall', 'DNS', 'ExpressRoute', 'VPN Gateway', 'BGP', 'AKS', 'App Service', 'SQL', 'PostgreSQL', 'Cosmos DB', 'Entra ID', 'incident', 'degraded', 'unavailable'.
Label unlabeled GitHub issues with priority and type labels. Use when triaging issues, cleaning up the backlog, or when asked to label/triage issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
日本語の概要は準備中です。原文の説明を表示しています。
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).
日本語の概要は準備中です。原文の説明を表示しています。
Consolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to clean up fingerprint sprawl. Decides between a one-shot merge of existing issues and a durable grouping rule that keeps future events from creating new fingerprints. Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。
Use when the user, inside an Orca terminal, asks Hermes to resolve, dispatch, orchestrate or supervise GitHub issues with Orca workers — 'orquestrar as issues 12, 15 e 18 no Orca', 'despachar as issues com label ready', 'coordenar workers do Orca para estas issues', or to resume such a Run after compaction. Do NOT use for a single unsupervised hand-off to another agent (Orca CLI directly), for working on one issue in this session (pwdev-feat feat-loop), or outside Orca.
日本語の概要は準備中です。原文の説明を表示しています。
Use quando um roadmap pwdev-roadmap/1 (roadmap.json) precisar ir para o GitHub — 'publicar o roadmap', 'criar as issues do roadmap', 'publish roadmap.json' — com issues, sub-issues, milestones, blocked-by e campos do Project, com dry-run, idempotente e retomável. Não use para uma issue avulsa (github-issues).
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
日本語の概要は準備中です。原文の説明を表示しています。
Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "既存プロジェクトのタスクを整理して", "技術的負債をIssue化して", "このコードベースを改善するタスクを洗い出して", "GitHub Projectに健全化タスクを登録して", "break down what needs to be fixed in this project", "surface tech debt as issues", or "create a project board for cleanup work". Diagnoses pain points and codebase health of an existing project, then registers improvement tasks as GitHub Issues and a Project Board.
This skill should be used when the user asks to "これらのIssueを全部実装して", "implement these issues autonomously", "Issue一覧を自動で片付けて", "これらのタスクを順番に実装してPRにして", or provides a list of GitHub Issue numbers/URLs for autonomous batch implementation. Fetches all specified Issues, resolves dependency order, then iterates through each — creating a worktree, implementing, and opening a PR — without user intervention.
OpenClawの複数のIssueやPRについて、担当を分けて原因調査と修正、検証を進め、許可された範囲でマージや解決済み案件のクローズまで管理するスキル。
GitHubのローカル保存データからIssueやPR、重複候補を調べ、同期状況や情報の不足を確認しながら、判断前に最新の状態を照合するスキル。
GitHubのIssueやPRを確認・作成し、コメントやレビュー、CIの実行結果を扱います。失敗ログの調査や再実行、承認されたマージの状態確認にも対応します。
課題や外部からのPRを分類し、報告内容の検証や不足情報の整理を進めます。対応状況を管理し、エージェントや人が着手するための作業説明を残すスキル。
GitHubの課題やプルリクエストを仕分けし、実行予定の作業をLinearにつなげて、公開状況と社内の担当・優先度・次の対応を整理するスキル。
Jiraの課題を取得し、要件やテスト条件を整理するスキルです。進捗コメントの追加、ステータス変更、課題検索を開発作業の流れで扱えます。
GitHubのIssue分類やPRの確認、CI失敗の調査、変更履歴を含むリリース準備、セキュリティ警告の確認を、gh CLIで進める運用スキル。
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
日本語の概要は準備中です。原文の説明を表示しています。
Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.
日本語の概要は準備中です。原文の説明を表示しています。