'issues' 검색 결과

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.

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

Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.

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

• Group QA findings by release
• Classify bugs by severity
• Apply labels to multiple issues and pull requests

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

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 Linear or Jira backlogs through the Composio CLI, a command-line tool. Fetch issues in bulk, group likely duplicates, update labels, priorities, and owners, then share a summary of changes in Slack.

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

• Weekly reviews of unassigned or stale issues
• Post-release bug reviews and owner assignment
• Grouping duplicate reports and linking related issues

Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.

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

Manages Linear issues, teams, and projects via CLI. Lists issues, creates tasks, views details, links issues, and runs GraphQL queries. Must use for "my Linear issues", "create Linear task", "link issues in Linear", "Linear API query", or any Linear project management request.

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

Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available. Not for browsing the existing issue tracker. Use oss-find-issue for that.

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

PRD 到研发 Issue 拆解 / implementation issues：当用户已有 PRD、需求文档、handoff、产品方案或 GitHub PRD issue， 需要拆成可独立领取、可验收、适合 GitHub Issues 承接的开发任务时使用。可用中文唤起： “把 PRD 拆成 issue”“需求文档拆任务”“生成 GitHub issues”“PRD 拆工单”“拆 implementation issues” “按 vertical slice 拆开发票”。不用于从零写 PRD；那类请求用 prd-architect。不用于评审 PRD 是否完整； 那类请求先用 prd-review。

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

Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.

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

OpenClaw의 PR과 Issue가 기존 작업과 중복되는지 근거로 판단하고, prtags에서 관련 작업을 하나의 그룹으로 묶어 판단 이유와 확신도를 기록합니다.

• PR과 기존 작업의 중복 여부를 확인합니다
• 같은 문제를 보고한 Issue를 찾습니다
• 관련 작업을 하나의 중복 그룹으로 묶습니다

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

Organize GitHub issues, synchronize project boards, and plan sprints, or short work cycles. Coordinate multiple AI agents to break issues into tasks, assign work, update progress, and track dependencies across a project.

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

• Sort issues and assign labels and priorities
• Break large issues into tasks for AI agents
• Synchronize project boards with task progress

Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.

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

• Reviewing a backlog of open issues and pull requests
• Checking whether reported bugs are already fixed
• Assessing pull request readiness for merging

Manage work on a SeaClip-Lite project board through commands that create and update issues, control pipelines, configure schedules, and inspect recent activity, with JSON output for AI agents.

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

• Find issues by status or priority
• Create issues and move them between board columns
• Start, resume, or stop work pipelines

Check web pages and components for accessibility issues against WCAG 2.2, web accessibility guidelines. Receive a report prioritized by user impact, or request targeted code fixes followed by verification of resolved and newly introduced issues.

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

• Get a prioritized accessibility report for a page
• Audit accessibility patterns across components
• Fix reported issues and verify the changes

Review open GitHub pull requests and issues to rank useful, lower-risk actions. Produce a prioritized report covering merge candidates, already-fixed issues, small fixes, branch verification, and contributor credit, with public comments drafted for approval.

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

• Prioritizing a crowded pull request and issue queue
• Finding small contributions to include before a release
• Identifying already-fixed issues with supporting evidence

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

Manage Jira issues through natural language using jira CLI or Atlassian MCP, a tool connection. Search and view tickets, draft new issues, update assignments or status, and check sprints, with review and approval before changes.

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

• Checking the details of an issue by its key
• Listing tickets assigned to you
• Drafting and creating a new issue

Turn the latest Granola call into action items with owners, teams, due dates, and matching existing Linear issues. It uses cognee memory of calls, issues, and Gmail, then prints the results or posts them to configured Slack.

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

• Extract action items from the latest Granola call
• Match follow-up tasks to existing Linear issues
• Clarify owners, teams, and due dates using email context

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

Manage Linear issues and projects through natural-language requests. Review priorities, create and update tickets, inspect team workloads, and organize release plans using a workflow that reads existing information before making changes.

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

• Prioritize bugs by their impact on users
• Plan issues and assignments for the next sprint
• Review workloads and redistribute assignments

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.

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

• Grouping open issues and identifying duplicates
• Checking whether reported bugs are fixed on main
• Drafting replies and issue closure comments

Organize Jira issues, plan sprints, and define workflows with clear ownership and acceptance criteria. Get help writing JQL, Jira's query language, to find stalled work, review workloads, and support project reporting.

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

• Organizing issues and acceptance criteria
• Planning sprints from recent team performance
• Finding stalled issues and blockers with JQL