'issue' 검색 결과

GitHub Issueを作成してGitHubに投稿するスキル。「Issueを作成」「Issue作成」「Issueにして」「Issueとして投稿」「GitHubにIssue」「create issue」「open issue」「バグ報告」「機能追加をIssueに」「改善提案をIssueに」などの依頼でトリガーする。コンテキスト収集→Issue本文生成→ラベル存在確認・作成→gh issue create投稿の流れでIssueを作成する。

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

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.

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

• Draft responses to unanswered issues
• Classify bugs and feature requests
• Review dosubot answers

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.

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

• Finding open issues outside a masterplan
• Distinguishing missing parents from missing plan ancestors
• Checking issue organization in automation

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.

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

• Turning implementation plan phases into GitHub Issues
• Updating existing issues to reflect a plan
• Structuring feature and chore work with issue templates

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.

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

• Sorting a growing backlog of open issues
• Checking whether suspected duplicate issues are truly duplicates
• Prioritizing security risks and breaking changes

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.

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

• Classifying unlabeled GitHub issues
• Filling missing label categories on open issues
• Reviewing a specific issue or numbered range

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.

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

• Consolidating bug reports that share a root cause
• Turning an issue backlog into a repair roadmap
• Routing new bugs into existing plans

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.

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

• Grouping issues into a release milestone
• Assigning owners to multiple issues
• Moving issues to a renamed or newly created milestone

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.

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

• Turn a specification into a feature request issue
• Check existing issues before registering a request
• Update an existing issue with specification requirements

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.

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

• Find other open issues a PR may resolve
• Check whether a PR conflicts with requested behavior
• Prepare evidence for related-issue reviews

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 を参照。

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

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.

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

• Draft issue replies with fixes and validation steps
• Post evidence-based pull request review findings
• Review batches of issues and pull requests

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.

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

• Finding requirements missing from an implementation
• Turning unmet requirements into GitHub issues
• Checking for duplicate issues before creating tasks

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.

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

• Deciding which open issues need immediate fixes
• Preparing a queue of feature requests and quality improvements
• Reviewing older issues and reports that need more evidence

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.

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

• Updating an issue after Factory work is complete
• Removing triage labels from completed work
• Adding a pending-close label and completion comment

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.

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

• Clean up resolved issues left open
• Link issues to pull requests with pending fixes
• Estimate priorities and change sizes for outstanding work

Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.

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

• Sort accumulated bug reports and feature requests
• Check possible duplicates against open and closed issues
• Review inactive issues for follow-up or closure

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.

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

• Review new and spiking errors every hour
• Avoid duplicate GitHub issues for Sentry errors
• Create issues with stack traces and impact details

Query GitHub issues and extract or summarize selected fields using jq, a JSON filtering tool. Inspect data structure and size before retrieving detailed results, then filter by status, author, labels, comments, or creation date.

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

• Finding issues with a specific label or author
• Counting retrieved issues by status
• Identifying old issues or active discussions

로컬에 저장된 GitHub 데이터에서 Issue, PR, 중복 후보를 찾습니다. 동기화 상태와 정보 누락을 확인하고 판단 전에 최신 상태를 대조합니다.

• 결함과 관련된 Issue와 PR을 찾을 때
• 중복 후보 Issue를 확인할 때
• 대응 결정 전에 저장 정보의 최신성을 확인할 때

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.

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

• Turning a feature idea into a GitHub issue
• Preparing a bug report using the project template
• Writing an issue in English and Chinese

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

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

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

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