3.9K skills · sorted by relevance
GitHub Issueを作成してGitHubに投稿するスキル。「Issueを作成」「Issue作成」「Issueにして」「Issueとして投稿」「GitHubにIssue」「create issue」「open issue」「バグ報告」「機能追加をIssueに」「改善提案をIssueに」などの依頼でトリガーする。コンテキスト収集→Issue本文生成→ラベル存在確認・作成→gh issue create投稿の流れでIssueを作成する。
The English summary is being prepared. Showing the original description.
Review Ant Design GitHub issues and prepare responses, labels, and closure recommendations. It distinguishes bugs from feature requests, checks bot answers, and presents a complete plan for approval before making changes.
Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.
Turn implementation plan phases into GitHub Issues with structured titles, descriptions, and labels. Check existing issues first, then create or update one issue per phase using feature or chore templates where available.
Organize open GitHub issues by category, risk, linked pull requests, duplicate candidates, and inactivity. Optionally analyze selected issues in depth, draft responses, and apply approved comments, labels, or closures to keep the backlog actionable.
Organize GitHub issues by reading their full descriptions and adding labels for type, effort, priority, and affected area. Preserve existing labels, fill missing categories, and summarize the reasoning alongside duplicate, related, or blocking issue relationships.
Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.
Assigns a specified set of GitHub issues to a milestone, owners, or both. Checks that each target is an open issue, applies changes individually, and reports results with verification of milestone counts and selected issue details.
Turn a specification file into a GitHub feature request issue. The skill extracts requirements, checks existing issues, and creates or updates one issue covering the specification, using a template to organize the problem, solution, and context.
Find open issues affected by a proposed code change. Identify additional problems it may fix or requested behavior it may conflict with, then report supporting code differences, issue symptoms, and confidence levels.
Phase 分割された GitHub Issue ツリーを新規作成するスキル。「イシューツリー作って」「タスクを Phase 別に Issue 化」「Issue ツリーを起票して」で使用。 要件・タスク一覧を受け取り、タスク分解（既定 2h 粒度・--granularity で変更可）→ Phase 分割 → ルート（トラッキング）issue → Phase 親 issue → 子 issue の階層を sub_issues API で紐付け。 phase ラベル付与・ルート issue 本文の Phase 別表生成まで自動化。任意の phase 指定で部分起票にも対応。 ツリーの棚卸し・更新は update-issue-tree、実装消化は implement-issue-tree を参照。
The English summary is being prepared. Showing the original description.
Help DeerFlow maintainers investigate GitHub issues and review pull requests, or proposed code changes. It prepares or posts evidence-based comments with fix strategies, risks, and validation guidance, and compares competing proposals for the same issue.
Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.
Review open GitHub issues for herdr and organize them into a concise Markdown table. Each row shows urgency, a recommended action, issue age, reactions, and a short reason to help decide what needs attention.
Update the GitHub issue linked to completed Factory work after verifying the target repository. Remove specified triage labels and, for open issues, add a pending-close label and completion comment without closing the issue.
Organize open GitHub issues and pull requests using the gh CLI, GitHub's command-line tool. Identifies resolved issues and pending fixes, estimates priorities and change sizes locally, and proposes closures, links, reviews, or merges for approval.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.
Turn a feature idea or bug description into a GitHub issue, informed by relevant code and existing issues. It prepares an English draft with a Chinese translation, incorporates feedback, and submits it with labels after explicit approval.
Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.
Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.
GitHub Issue を作成する。タスクは Issue 本文内でチェックボックスに分割。「Issue 作成」「Issue を作って」「タスクを Issue に」「Issue 追加」「チケット作成」「Issue を切る」「タスクを分割して Issue」などで起動。「ブランチも」「worktree も」と伝えれば作成後にブランチ/worktree も用意する。
The English summary is being prepared. Showing the original description.
オープン Issue の一覧を優先順位付きで表示する。「Issue 一覧」「Issue リスト」「オープン Issue」「Issue を見せて」「チケット一覧」「未解決 Issue」「Issue 確認」などで起動。優先度順にソートして表示。「クローズ済みも」「自分の Issue」などの絞り込みは発話から判断する。
The English summary is being prepared. Showing the original description.
既存の GitHub Issue ツリーを棚卸し・更新するスキル。「ツリーを棚卸しして」「イシューツリーを更新して」「トラッキング issue を整理して」で使用。 ルートのトラッキング issue 番号を受け取り、sub_issues API でツリー全体を再帰取得 → closed 親下の残置 open issue 付け替え・孤児の再配置・新 Phase 親の新設・phase ラベル同期 → ルート issue 本文は既存本文を保持し、Phase 別表・棚卸し履歴の管理ブロックのみ更新する。 ツリー新規作成は create-issue-tree、実装消化は implement-issue-tree を参照。
The English summary is being prepared. Showing the original description.