'issues' 검색 결과

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

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

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

repo の root に issues/ を作り、dotfiles の issues/README.md を持ち込んで issue 運用を始める。commit するかはユーザーに聞く。「issue運用を始めて」「issuesディレクトリを作って」「start-issues-ops」で発火。

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

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

Organize GitHub issues using parent and child relationships and links showing which tasks must finish first. Use gh CLI to create, change, remove, and inspect relationships, including links across repositories.

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

• Breaking a large issue into linked sub-issues
• Recording which issues must be completed first
• Linking dependent issues across repositories

Review Azure infrastructure code and deployed resources against five Well-Architected Framework pillars. Identify configuration drift, classify risks, and produce remediation guidance and an architecture diagram, with GitHub issues created after user approval.

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

• Review Azure reliability and security risks
• Compare infrastructure code with deployed resources
• Assess opportunities to improve cost and performance

Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.

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

• Define feature requirements and scope in a PRD
• Split development plans into tasks and sync them to GitHub
• Coordinate parallel agents working on issues

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

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

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

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

Collect new feedback from configured Slack and GitHub Issues sources, acknowledge receipt, analyze recordings, and verify claimed fixes against the default branch. Combine unresolved items into a rolling plan ready for the lfg workflow.

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

• Collecting feedback from Slack and GitHub Issues
• Analyzing recordings attached to feedback
• Verifying that reported fixes were merged

Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.

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

• Create issues from validated security findings
• Find and reuse existing issues for the same finding
• Register a reviewed batch of security issues

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

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

Work with Jira issues through Orca's command-line interface. Search issues, move them through workflow states, create follow-up issues, and record completion with a PR or MR link and a comment using guidance matched to the installed Orca version.

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

• Working from a linked Jira issue
• Searching issues with JQL
• Moving issues through workflow states

Create and organize GitHub issues with templates, labels, assignees, and milestones. Coordinate multiple agents to track progress, post updates, and manage related issues across repositories as part of a shared project workflow.

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

• Creating related feature, bug, and documentation issues
• Posting progress updates on complex issues
• Organizing issues by priority and milestone

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

Review GitHub issue discussions and code on the target branch to confirm a fix has landed, then close resolved issues with evidence, contributor credit, and an invitation to reopen if the problem returns.

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

• Closing issues after confirming fixes have landed
• Reviewing resolved issues before a release
• Posting progress notes for partial fixes

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

This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.

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

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, manage repository labels, 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", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.

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

Triage application logs, open GitHub issues, pending feedback, in-app Issues, and agent conversations. Runs five phases: logs → close shipped issues → feedback → in-app issues → agent FAQ gaps. Use when /whats shows pending feedback, checking app logs, cleaning up shipped issues, or working the in-app Issues backlog.

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

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.

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