'issues' 검색 결과

Connect Claude to external apps through Composio to send emails, create issues, post messages, and update data. It also supports linked tasks, such as summarizing GitHub issues and posting the results to Slack.

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

• Send an email through Gmail
• Create a GitHub issue with a label
• Post a deployment update to Slack

Connect Claude to external apps to send emails, create GitHub issues, post Slack messages, and add notes to Notion. Composio Tool Router selects the appropriate tool and executes the requested action after authorization.

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

• Sending emails through Claude
• Creating GitHub issues
• Posting messages to Slack

Review and manage issues, projects, and planning data in Linear. Use it to examine development cycles, find carried-over tickets and release blockers, and update issue status, assignees, priorities, or milestones with the required access.

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

• Reviewing sprints and development cycles
• Finding tickets carried over into the next cycle
• Identifying issues blocking a release

Audit a website for problems affecting search visibility, from search engine access and indexing to speed, page titles, content, and links. Receive evidence-based findings and a prioritized action plan, including checks for multilingual and local business sites.

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

• Investigating a drop in search traffic or rankings
• Reviewing page titles and internal links
• Checking multilingual search settings

Find where Multica’s issue management guidance has moved and how to replace retired metadata guidance. This redirect points older task briefs to the current skill and explains where different kinds of issue information belong.

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

• Find current guidance from an older task brief
• Check alternatives to retired issue metadata
• Locate rules for linking pull requests to issues

Audit a live web page for accessibility issues and produce a fix worklist with exact element selectors, evidence, and suggested changes. Findings include impact counts and source locations when available, without editing the application.

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

• Check accessibility after a UI change
• Locate contrast and accessible-name issues
• Prepare a fix worklist with element selectors

Compare accessibility findings between two versions of a web page. Identify newly introduced and fixed issues, count existing findings, and report evidence and suggested fixes without editing application code.

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

• Check accessibility before committing local changes
• Compare a page against a branch baseline
• Confirm which accessibility issues a change fixed

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

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

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Review Git changes with the ocr command-line tool and a configured AI model. Get line-level findings grouped by severity for working changes, commits, or branch comparisons, with code fixes applied when explicitly requested.

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

• Reviewing changes before a commit
• Checking a pull request or branch comparison
• Inspecting a specific commit for issues

Explore a web application as a user to find reproducible bugs and usability problems. Produce a structured report with reproduction steps, screenshots, and videos for interactive issues, giving responsible teams concrete evidence to investigate.

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

• Checking a web app's quality before release
• Testing forms and common user workflows
• Finding confusing interfaces and visual problems

Scan a codebase or selected changes for security issues, then request targeted patch files for findings. Independent agents verify reported issues and proposed fixes, while you review and apply patches yourself.

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

• Auditing an entire repository or a selected area
• Checking security issues in branch or pull request changes
• Scanning a single commit

Use the authenticated gh command-line tool to inspect GitHub issues, review proposed code changes, search code, check automated workflow runs, and manage releases. Changes to GitHub are made only when explicitly requested.

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

• Reading and triaging GitHub issues
• Creating and reviewing pull requests
• Searching repository code

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

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

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Analyze AWS infrastructure definitions, deployed resources, usage metrics, and actual costs to identify savings opportunities. Rank recommendations by savings, risk, and effort, then create individual GitHub issues and a coordinating issue after approval.

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

• Identify underused AWS resources
• Estimate monthly savings from configuration changes
• Prioritize cost reductions by risk and implementation effort

Review AWS infrastructure code and deployed resources against the six Well-Architected pillars. Produce risk-ranked findings, remediation examples, and an architecture diagram, then create GitHub issues for tracking improvements after user confirmation.

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

• Review AWS infrastructure code and deployed resources
• Prioritize findings by risk
• Prepare infrastructure code remediation examples

Assess an AWS resource using CloudWatch logs and metrics, the measurements that describe its behavior. Investigate failures and performance issues, classify their severity, and produce a remediation report with staged actions, CLI commands, and monitoring recommendations.

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

• Investigate Lambda errors and throttling
• Examine RDS performance and connection issues
• Check ECS task counts and service health

Helps build and maintain Ant Design interfaces by checking component options, examples, and theme settings. It also supports debugging, version migrations, and project scans to identify deprecated code and configuration issues.

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

• Build interfaces using component APIs and working examples
• Investigate component bugs and configuration issues
• Check changes before upgrading Ant Design

Organize customer support emails, turn requests into tasks, and record ticket updates in a tracking spreadsheet. Escalate urgent issues through Google Chat and schedule follow-up calls with customers in Google Calendar.

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

• Sort and prioritize support emails
• Turn customer emails into support tasks
• Record ticket status in a tracking spreadsheet

Coordinate multiple agents to maintain context-mode, from sorting GitHub issues and reviewing pull requests to preparing releases and announcements. Workflows require reproduced bugs, source evidence, test-first changes, and checks across supported platforms.

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

• Investigating reported bugs and their history
• Reviewing contributor pull requests
• Preparing releases and compatibility checks

Review open GitHub issues, proposals, and pull requests to identify useful maintainer work. Get ranked candidates with evidence, dependencies, and validation needs, then begin work only on an item you explicitly select.

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

• Choose the next maintenance task
• Prioritize a backlog for the available work window
• Find pull requests that need review

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

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