'issues' 검색 결과

Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.

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

• Investigating the root cause of a reported bug
• Checking for duplicate issues or regressions
• Preparing findings for whoever plans the fix

Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.

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

• Checking whether reported bugs belong to @mastra/core
• Labeling confirmed core bugs with supporting evidence
• Previewing issue classifications without changing GitHub

Review Qwen Code issues and pull requests through staged checks. Assess product fit, code simplicity, and CI evidence, then prepare English and Chinese comments that explain findings and flag decisions needing maintainer attention.

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

• Triage incoming Qwen Code issues
• Check pull requests against product direction
• Review changes for unnecessary complexity

Audit a website’s technical setup, page elements, and content for search visibility issues. Produce page and site health scores, evidence-backed findings, and a prioritized action plan covering urgent fixes, practical improvements, and longer-term work.

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

• Investigating falling search traffic or rankings
• Reviewing page titles, headings, and internal links
• Checking SEO before or after a site migration

Manage Jira issues, build JQL searches, and design project workflows and reports. Use bundled scripts to generate search queries and check workflow designs, with guidance on which operations require Jira’s interface or API.

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

• Finding overdue or stale Jira issues
• Creating issues and updating their status
• Checking workflow designs for unreachable states

Audit a codebase before production deployment across eight areas, including security, databases, dependencies, and AI usage. Receive findings with file locations, manual checklists, and a release verdict that blocks shipping when critical issues remain.

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

• Check an application before its first production release
• Find security and database issues before deployment
• Review backup restoration and rollback readiness

Inspect production errors recorded in Sentry using read-only queries. The skill summarizes recent issues, retrieves details of individual error occurrences, and accesses AI-generated cause analysis or fix plans through the command-line tool.

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

• Reviewing unresolved production issues from the last 24 hours
• Inspecting an issue by its short ID
• Checking individual error occurrences and release details

Create and manage GitHub issues for the Kilo VS Code extension or JetBrains plugin using gh, GitHub's command-line tool. Guides template selection, clear titles, required project board assignment, and authentication permissions.

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

• Reporting a bug in the VS Code extension
• Requesting a feature for the JetBrains plugin
• Filing usage or design questions

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

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

Review a single web page for search optimization, covering titles, content, technical settings, images, and structured data that describes the page to search engines. Receive category scores, prioritized issues, practical recommendations, and suggested markup.

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

• Check an article or landing page for SEO issues
• Review page titles, descriptions, and heading structure
• Find image issues and potential performance problems

Manage GitHub collaboration through the gh command-line tool and GitHub APIs. Create and review pull requests, organize issues, investigate failed Actions workflows, check automated tests before merging, and prepare releases with generated notes.

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

• Creating a pull request with a clear description
• Organizing issues with labels and milestones
• Investigating failed Actions workflows

Use Claude to send emails, create GitHub issues, post Slack messages, and add notes to Notion through Composio CLI, a terminal tool. It connects these tasks to actions in external apps.

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

• Send launch announcements through Gmail
• Create GitHub issues for bugs
• Post deployment updates to Slack

Use Codex to send emails, create issues, post messages, and update data in connected apps through Composio CLI, a terminal tool. It supports services including Gmail, Slack, GitHub, and Notion.

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

• Send emails through Gmail
• Create GitHub issues
• Post updates to Slack

Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.

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

• Recurring preparation of fixes for Sentry issues
• Drafting replies to Front tickets
• Preparing small performance improvement PRs

Find Linear issues reporting the same underlying bug, compare their evidence, and propose which issue to keep. After approval, transfer unique findings and relevant people’s details, then close duplicates with links to the surviving issue.

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

• Clean up duplicate bug reports in a backlog
• Check whether a bug has already been reported
• Consolidate reproduction steps and logs

Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.

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

• Assessing newly reported GitHub issues
• Finding duplicate reports and recurring bugs
• Reproducing bugs and recording the results

Review code changes and files for bugs, security risks, performance problems, design issues, and test coverage. Receive a structured report with prioritized findings, concrete improvement examples, positive feedback, and an overall review verdict.

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

• Reviewing a pull request
• Auditing code quality and security
• Finding refactoring opportunities

Review recent changes, automated test failures, issues, and conversations to prioritize engineering work. Produce a concise report separating urgent actions, watch items, noise, and state updates, with suggested next steps and rough effort estimates.

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

• Prioritizing recent CI and test failures
• Sorting team issues and conversation findings
• Separating urgent work from items to monitor

Reviews recent changes, CI failures, open issues, pull requests, and conversations to produce a prioritized findings report. It separates urgent work from monitoring and noise, suggests next actions, and records facts for the next automated review cycle.

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

• Prioritizing recent CI and test failures
• Reviewing blocked pull requests and unanswered issues
• Preparing next actions for an automated work cycle

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

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

Review open GitHub issues and pull requests against project templates and contribution guidelines. Get a report on missing information and compliance, with options to apply recommended labels or close incomplete submissions with an explanatory comment.

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

• Reviewing open issues in bulk
• Checking pull requests against templates
• Applying labels based on review results

Review a product launch against the team's legal framework and risk standards. Produce a category-by-category memo with required actions, owners, and deadlines, plus a separate tracker comment that omits internal legal reasoning.

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

• Reviewing legal issues before a product launch
• Listing required actions, owners, and deadlines
• Checking privacy and AI issues in a new feature