Results for “issue”

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Review AWS infrastructure code and deployed resources against the six Well-Architected pillars. Produce risk-ranked findings, remediation examples, and an architecture diagram, then create GitHub issues for tracking improvements after user confirmation.

• Review AWS infrastructure code and deployed resources
• Prioritize findings by risk
• Prepare infrastructure code remediation examples

Analyze Azure infrastructure definitions, deployed resources, usage metrics, and pricing to identify cost reductions. Rank recommendations by savings, risk, and effort, then create individual GitHub issues and a coordinating EPIC issue after user approval.

• Finding Azure resources with oversized service tiers
• Comparing storage and database cost reduction options
• Prioritizing savings by risk and implementation effort

Attach screenshots, images, or videos to GitHub pull requests and issues using GitHub CLI. It also covers embedding images within comment text, adding alternative text, and retrieving an uploaded asset’s URL from the posted comment.

• Attach a screenshot to a pull request
• Add a video to an issue report
• Embed an image within a GitHub comment

Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.

• Implement an accepted issue within its agreed scope
• Repair a classified pull request finding
• Validate failure, recovery, and cleanup behavior

Assess OpenShell issues by checking first-hand use cases, reproduction evidence, existing behavior, and duplicates. Prepare a concise technical assessment, request specific missing information, and leave acceptance and roadmap decisions to human maintainers.

• Checking reproduction evidence for a reported bug
• Clarifying a feature request’s use case and alternatives
• Identifying duplicates or already-fixed behavior

Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.

• Submit code changes for review
• Open a draft pull request
• Link a pull request to its issue

Helps clarify bug reports written by people, search for duplicate reports, and collect diagnostic evidence. Keeps investigation material separate from a concise issue draft, with the detailed workflow defined in a referenced file.

• Clarify an unclear bug report
• Search for duplicate bug reports
• Collect diagnostic evidence

Review open issues and discussions to create a clear work queue. Record the five highest-priority items, suggested labels, possible duplicates, and cases needing human judgment in a state file for future reviews.

• Prioritizing a backlog of open issues
• Finding possible duplicate reports
• Preparing label suggestions

Develop user-visible improvements for cc-wf-studio, verify their basis in the code, and assess their value. Record qualifying proposals as locked GitHub issues, creating a queue of concrete ideas for later implementation without changing code.

• Proposing improvements users would notice
• Checking ideas against code and existing proposals
• Preparing an implementation queue

Inspect GitHub pull requests, issues, and automated workflow runs using the gh command-line tool. Check PR status, investigate failed jobs, and retrieve structured JSON or API data without opening a browser.

• Checking pull request status and automated checks
• Investigating failed CI jobs and their logs
• Listing issues and pull requests

Use the gh command-line tool to work with GitHub issues, pull requests, and automated checks. Inspect failed workflow steps and logs, retrieve additional data through the API, and extract selected fields from structured results.

• Check automated test status on a pull request
• Inspect logs from failed workflow steps
• List issue numbers and titles

Diagnose failed canary ferry runs, automated checks for failures or regressions, when invoked by CI with the required context. It gathers logs, classifies the cause, and files a GitHub issue with supporting evidence.

• Investigate GPU or TPU canary failures triggered by CI
• Distinguish infrastructure failures from training or metric problems
• File a GitHub issue with logs and run context

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで役割を分けて進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

The English summary is being prepared. Showing the original description.

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

The English summary is being prepared. Showing the original description.

JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).

The English summary is being prepared. Showing the original description.

直近N日（デフォルト1日）に更新された `cc-triage-scope` / `cc-pr-created` ラベル付きGitHub Issueのdescriptionとコメントを横断し、繰り返し現れる仕様判断・要件決定のロジックを再利用可能なルールとして抽出して `.claude/requirements/` 配下のタイプ別マークダウンへ集約・統合・圧縮したうえで、commit-push + create-prでPRを作成する（`cc-triage-scope`ラベル + 自分自身をAssignee）。作成したルールは create-issue / create-issue-from-issue-number / answer-issue-questions が仕様作成・判断の材料として読み込む。

The English summary is being prepared. Showing the original description.

Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.

• Reviewing issue and pull request sweep reports
• Creating a repair job from an existing report
• Investigating failed GitHub Actions runs

Turn an existing discussion and codebase knowledge into a specification, then publish it to the project's issue tracker. Organize the problem, user needs, implementation decisions, testing approach, and work excluded from scope.

• Turning a feature discussion into a specification
• Publishing agreed requirements to the project issue tracker
• Documenting implementation and testing decisions

Summarize the past 24 hours of GitHub pull requests, review requests, issues, CI runs, and merges in a daily briefing. The GitHub-style page highlights pending reviews and failed automated checks.

• Reviewing the past 24 hours of GitHub activity
• Checking pending review requests
• Spotting failed CI checks

Organize GitHub work through task-specific modes for pull request reviews, issue tracking, releases, and branch management. Coordinate repository synchronization and CI/CD, the workflows that test and deploy changes, with support for multiple agents.

• Coordinating pull request reviews and merges
• Organizing issues and tracking progress
• Managing releases and CI/CD workflows

Investigate LazyCodex and Codex bugs using reproduction results and source code. Identify the responsible repository, then prepare or submit an English GitHub report with evidence, likely causes, fix guidance, and a verification plan.

• Report a reproducible LazyCodex or Codex bug
• Identify which project owns a defect
• Add new evidence to an existing issue

Diagnose OpenCLI commands broken by website changes, collect execution traces, patch the adapter that connects to the site, and retry. After a verified repair, prepares a GitHub issue for submission with user approval.

• Repair commands broken by website layout changes
• Adapt to changed API responses
• Distinguish empty results from adapter failures