'issue' 검색 결과

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an approved security remediation plan
• Rechecking a reviewed fix against current code
• Adding regression tests for a security boundary

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

OpenClaw의 여러 Issue와 PR을 담당자별로 조사하고 수정·검증하며, 허용된 범위에서 병합과 해결된 항목의 종료까지 관리합니다.

• 여러 Issue와 PR의 수정을 관리합니다
• 기존 수정 PR을 마무리합니다
• 수정된 Issue를 검증하고 닫습니다

GitHub의 Issue를 조건별로 골라 백그라운드 에이전트에 수정, 테스트, PR 생성을 맡깁니다. 중복 작업을 피하고 리뷰 지적 대응도 다룹니다.

• 라벨이나 담당자로 문제 선택
• 여러 문제의 수정 PR 생성
• 생성한 PR의 리뷰 지적 대응

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

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

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

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

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

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

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

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

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

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

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

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

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

Extend safe-output jobs, which execute agent-generated actions, to reference newly created issues through temporary IDs. The guide covers job dependencies, issue-number resolution, input validation, tests, and warning-based handling of unresolved references.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Linking sub-issues to a parent created in the same run
• Adding temporary ID resolution to another safe-output job
• Testing temporary ID validation and job dependencies