跳到正文
cccskills

“issue”的搜索结果

4136 个 · 按相关度排序

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.

中文简介正在准备中。当前显示英语简介。

  • Creating an implementation plan from a GitHub issue
  • Implementing an authorized issue with focused tests
  • Updating documentation alongside behavior changes
NVIDIA/OpenShell1.7万2026年10月21日 更新

オープン Issue の一覧を優先順位付きで表示する。「Issue 一覧」「Issue リスト」「オープン Issue」「Issue を見せて」「チケット一覧」「未解決 Issue」「Issue 確認」などで起動。優先度順にソートして表示。「クローズ済みも」「自分の Issue」などの絞り込みは発話から判断する。

中文简介正在准备中。当前显示原文说明。

shiiman/claude-code-plugins62026年6月17日 更新

GitHub Issue を作成する。タスクは Issue 本文内でチェックボックスに分割。「Issue 作成」「Issue を作って」「タスクを Issue に」「Issue 追加」「チケット作成」「Issue を切る」「タスクを分割して Issue」などで起動。「ブランチも」「worktree も」と伝えれば作成後にブランチ/worktree も用意する。

中文简介正在准备中。当前显示原文说明。

shiiman/claude-code-plugins62026年6月17日 更新

プロジェクトのドラフトアイテム (DraftIssue) を実 GitHub Issue に変換し、Status/Priority/Size 等のフィールド値を引き継ぐ。親 Issue を指定または新規作成して `gh api .../sub_issues` で sub-issue として紐付け可能。「ドラフトを Issue 化」「DraftIssue を変換」「プロジェクトのタスクを Issue にして」などで使用。

中文简介正在准备中。当前显示原文说明。

Fandhe-AI/agent-reference-skills42026年10月20日 更新

既存の GitHub Issue ツリーを棚卸し・更新するスキル。「ツリーを棚卸しして」「イシューツリーを更新して」「トラッキング issue を整理して」で使用。 ルートのトラッキング issue 番号を受け取り、sub_issues API でツリー全体を再帰取得 → closed 親下の残置 open issue 付け替え・孤児の再配置・新 Phase 親の新設・phase ラベル同期 → ルート issue 本文は既存本文を保持し、Phase 別表・棚卸し履歴の管理ブロックのみ更新する。 ツリー新規作成は create-issue-tree、実装消化は implement-issue-tree を参照。

中文简介正在准备中。当前显示原文说明。

Fandhe-AI/agent-reference-skills42026年10月20日 更新

openclaw-repair-sweep

OpenClaw 官方免费有简介AI 评分 90分

管理OpenClaw的多个Issue和PR,分配负责人调查原因、修复并验证,在获准范围内推进合并及关闭已解决事项,同时记录证据和进度。

  • 管理多个Issue或PR的修复
  • 完成已有的修复PR
  • 验证并关闭已修复的Issue
openclaw/openclaw39.3万2026年10月21日 更新

gh-issues

OpenClaw 官方免费有简介AI 评分 90分

按条件筛选GitHub的Issue,交给后台智能体完成修复、测试和PR创建。工作流会检查重复任务,也支持处理审核意见并定期监测新问题。

  • 按标签或负责人选择问题
  • 为多个问题创建修复PR
  • 处理已创建PR的审核意见
openclaw/openclaw39.3万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Classifying newly opened GitHub issues
  • Requesting missing reproduction details
  • Identifying duplicates and existing fixes
mastra-ai/mastra2.9万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Distinguish bugs from unsupported configurations
  • Check whether an issue duplicates an earlier report or fix
  • Draft a GitHub issue reply with clear next steps
apache/shardingsphere2.1万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Preparing a bug report using the required issue form
  • Checking for duplicate feature requests
  • Adding information to an existing issue
Gentleman-Programming/gentle-ai78942026年10月21日 更新

fix-issue

免费

Resolve an identified GitHub issue through investigation, duplicate-work checks, implementation, and regression testing. Open a pull request, address CI and review feedback, and track the outcome while keeping the issue updated with concise progress comments.

中文简介正在准备中。当前显示英语简介。

  • Investigate and fix a specified GitHub issue
  • Check for overlapping issues and pull requests
  • Add a regression test for a reported bug
marin-community/marin39922026年10月21日 更新

feedback

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Report a Codewhale bug with reproduction steps
  • Submit a feature request for Codewhale
  • Check open issues for duplicate reports
codewhale-hq/Codewhale4.1万2026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Convert priority labels into a shared Priority field
  • Copy project priorities and due dates into issue fields
  • Preview migration changes without updating issues
github/awesome-copilot4万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • File bug reports and feature requests
  • Update issue owners, dates, and priorities
  • Organize parent tasks, subtasks, and dependencies
github/awesome-copilot4万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Investigate and fix several GitHub issues in parallel
  • Find issue candidates based on contribution history
  • Track progress and blockers for each issue
mastra-ai/mastra2.9万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Simplifying a lengthy bug report
  • Drafting an issue from a pull request
  • Clarifying the intended experience for a new feature
every-app/open-seo2.4万2026年10月20日 更新

Investigate a failed GitHub Actions job and turn its logs into a structured bug issue for Megatron-LM. Collects failing tests, errors, and related pull requests, checks for duplicates, and identifies an assignee from test history.

中文简介正在准备中。当前显示英语简介。

  • Create a bug issue from a failed GitHub Actions job
  • Summarize failing tests and relevant log excerpts
  • Check for an existing issue covering the same test
NVIDIA/skills36792026年10月21日 更新

GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。

中文简介正在准备中。当前显示原文说明。

Fandhe-AI/agent-reference-skills42026年10月20日 更新

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.

中文简介正在准备中。当前显示原文说明。

getty104/claude-task-worker42026年10月20日 更新

GitHub issue を新規作成・下書きするとき、または既存 issue の本文を書き直すときに必ず使うスキル。「issue を作って」「issue 化して」「これを issue にまとめて」のような依頼で発火し、`gh issue create` を直接呼ぶ前に必ず参照する。人間が合意した内容だけを、意味を足さずに issue へ残すための基準を定める。

中文简介正在准备中。当前显示原文说明。

rito528/dotfiles22026年10月21日 更新

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 a batch of issues or an entire milestone
  • Find issues already addressed by current code
  • Separate small fixes from design work and deferred items
codewhale-hq/Codewhale4.1万2026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Classify a newly opened issue
  • Review priorities and statuses for issues and pull requests
  • Triage unlabeled items in a batch
NVIDIA/NemoClaw2.3万2026年10月21日 更新

triage

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Classifying a newly reported issue
  • Checking which release lines a bug affects
  • Finding duplicates and related fixes
verdaccio/verdaccio1.8万2026年10月21日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Organizing a growing issue backlog
  • Selecting the top five actionable issues
  • Suggesting labels and possible duplicates
cobusgreyling/loop-engineering1.2万2026年10月21日 更新