'bugs' 검색 결과

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

Maintain VoiceStudio by investigating reported bugs, reviewing contributed changes, diagnosing automated check failures, and preparing requested releases. It guides focused fixes, testing, and packaging verification for the Electron app and Python backend.

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

• Investigating reported VoiceStudio bugs
• Reviewing contributor pull requests
• Diagnosing automated check failures

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

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

Test app interfaces on an Android emulator using ADB, a command-line device tool. Inspect element positions, perform taps and text entry, then check screenshots and React Native logs to verify behavior and investigate layout or interaction bugs.

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

• Verify app interfaces after UI changes
• Investigate layout and interaction bugs
• Check feature behavior through automated interactions

Capture unexpected behavior and workarounds encountered while using Prisma 8, Prisma Compute, or Prisma Postgres. Record symptoms, causes, versions, and reproduction steps in a local log linked to a Linear ticket, checking for duplicates first.

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

• Recording an unexpected Prisma error and its workaround
• Documenting undocumented behavior found in an example app
• Preserving reproduction steps from a customer report

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

Review Python code for common mistakes in error handling, asynchronous operations, type annotations, and tests. Use a practical checklist and correction examples to guide code reviews, investigate bugs, and improve existing implementations.

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

• Reviewing Python code before a merge
• Investigating bugs caused by common coding mistakes
• Refactoring legacy Python code

Create technical documentation that people and AI can navigate by separating facts, context, known bugs, and uncertain claims. Convert existing Markdown to HADS, a structured documentation format, and check its required elements.

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

• Write API documentation for people and AI
• Convert an existing README to HADS
• Check document structure and block formatting

Build and debug sglang tests comparing token probabilities during prompt processing and step-by-step generation. Separate numerical differences from reused-state bugs, choose test thresholds, and locate the first operation that diverges.

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

• Adding probability consistency tests for a model
• Choosing or justifying a kl_div threshold
• Separating numerical differences from cache state bugs

Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.

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

• Reproducing and fixing reported SDK bugs
• Investigating failing tests
• Fixing regressions in automated CI checks

Reviews pull requests for bugs, error handling, code quality, and style consistency. Organizes feedback into an overview, must-fix issues with file locations, improvement suggestions, and positive notes so reviewers can distinguish urgent problems from refinements.

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

• Finding bugs that must be fixed before merging
• Reviewing TypeScript types and asynchronous code
• Checking naming, imports, and leftover debug statements

Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.

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

• Investigating incorrect token rate displays
• Reproducing intermittent bugs with a real model
• Tracing flicker or stuck status displays

Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.

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

• Planning QA for a sprint or game feature
• Preparing manual test cases from acceptance criteria
• Recording test results, bugs, and screenshot evidence

Compare existing game tests with key paths in the game design document, find fixed bugs without tests to catch recurrence, and identify coverage gaps from new features. Maintain a release checklist of existing tests.

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

• Checking test coverage after a bug fix
• Auditing key gameplay paths before a release
• Finding test coverage gaps at sprint close

Create a game playtest report template or turn session notes into organized feedback. Separate gameplay problems from bugs, compare observations with design intent, and identify priorities for design changes, balance adjustments, and polish.

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

• Preparing a playtest report template
• Organizing raw playtest notes
• Separating gameplay issues from bugs

Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.

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

• Distinguish bugs from unsupported configurations
• Check whether an issue duplicates an earlier report or fix
• Draft a GitHub issue reply with clear next steps

Review code for security risks, logic bugs, and performance problems. Receive specific feedback explaining the affected lines or patterns, why they matter, and how to fix them, with required changes separated from optional improvements.

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

• Reviewing code changes before merging a pull request
• Checking input validation, access controls, and secret handling
• Finding inefficient queries and blocking operations

Review GitHub pull requests with specialized agents that check for clear bugs and violations of project instructions in CLAUDE.md. Validate bug findings before posting focused comments on the affected lines, with fix suggestions where appropriate.

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

• Reviewing a pull request for clear bugs
• Checking changes against CLAUDE.md rules
• Posting validated findings on affected lines

Diagnose errors and incorrect inference results in MNN's QNN backend for Qualcomm HTP processors. Compare intermediate calculation data against CPU results to locate the first faulty operator, distinguish bugs from precision limits, and guide operator support and performance fixes.

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

• Investigate QNN runtime and model conversion errors
• Find the first operator producing incorrect results
• Distinguish implementation bugs from numerical precision limits

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 code changed during a project phase for bugs, security vulnerabilities, and quality issues. Choose the review depth or specific files, receive findings grouped by severity, and optionally apply fixes followed by another review.

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

• Reviewing code changed during a phase
• Checking selected source files
• Examining interactions across files

Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.

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

• Review selected files in a critical code change
• Investigate concerns raised by an initial review
• Check complex state transitions and object lifecycles