3.9K skills · sorted by relevance
既存の 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.
Coordinate repairs across multiple OpenClaw issues or pull requests, which propose code changes. Assign owners, prove defects, verify fixes, and track outcomes through merging or closing resolved items within the authorized scope.
Turn GitHub issues into pull requests, proposed code changes ready for review. Filter issues, avoid duplicate work, and assign background agents to implement fixes, run tests, and optionally address review comments.
Triage a GitHub issue by reviewing its discussion, related issues, and fixing pull requests. Publish a concise comment with classification, severity, evidence, and the next action, then update a small set of triage labels.
Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.
Prepare and manage GitHub bug reports and feature requests using repository evidence and required forms. Check for duplicates, identify missing information, and verify published issues or comments before reporting the result.
Turn Codewhale bugs and feature ideas into GitHub issues. Gather reproduction details, check for duplicates, and present the exact draft for approval before submitting it and returning the issue link.
Move GitHub labels and Project V2 field values into organization-wide issue fields, structured properties shared across repositories. Review mappings and conflicts before migration, preserve existing values, and optionally remove migrated labels.
Create and update GitHub issues for bugs, feature requests, and tasks. Organize owners, labels, dates, and priorities, connect related work, and track dependencies and project progress through MCP tools and the GitHub API.
Coordinate multiple Mastra Code workers to investigate and fix GitHub issues in parallel. Keep each issue in a separate working directory, track progress in reports, review changes, and manage pull requests, reviewer feedback, and automated checks.
Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.
GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。
The English summary is being prepared. Showing the original description.
Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.
The English summary is being prepared. Showing the original description.
GitHub issue を新規作成・下書きするとき、または既存 issue の本文を書き直すときに必ず使うスキル。「issue を作って」「issue 化して」「これを issue にまとめて」のような依頼で発火し、`gh issue create` を直接呼ぶ前に必ず参照する。人間が合意した内容だけを、意味を足さずに issue へ残すための基準を定める。
The English summary is being prepared. Showing the original description.
Review a set of GitHub issues against their full discussions and current code. Produce a table separating completed work, small fixes, design work, and deferred items, with evidence, confidence levels, and next actions for each issue.
Review NemoClaw issues and pull requests, propose issue types, project priorities, statuses, and labels, then apply only approved changes. Supports individual items and batch triage, with explanations and a report of each update.
Assess Verdaccio issues against the code, affected release lines, and related reports. Distinguish bugs from configuration problems or duplicates, then propose existing labels, next steps, and a reply draft backed by evidence.
Review open issues and discussions to organize a project's backlog. Identify possible duplicates, suggest priorities and labels, and record the top five actionable items and cases needing human attention in a state file.
Turn a Codewhale bug or feature idea into an actionable GitHub issue with evidence, reproduction steps, and testable acceptance criteria. Check related work, select existing labels and a milestone, and return the filed issue with supporting evidence.
Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.
Create GitHub issues for OpenShell bugs, feature requests, and tasks using the gh command-line tool. Organize firsthand use cases, impact, and completion criteria into the project's templates, then return the created issue link.
Investigate a specific OpenShell problem or feature need and create a structured GitHub issue. Record observed behavior, technical findings, alternatives, and missing evidence so a human can decide what to accept and pursue.
INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.
The English summary is being prepared. Showing the original description.
雑な要件や思考メモからGitHub Issueを生成するスキル。 「Issueを作成して」「Issueを作って」「Issue起票して」「これをIssueにして」などのリクエストで発動。 テキスト入力や添付ファイルから要件を抽出し、構造化されたIssueを作成する。 記載されていない仕様は推測せず、不明点はユーザーに質問する。
The English summary is being prepared. Showing the original description.