'bugs' 검색 결과

Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.

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

• Adding a reported bug to the Remotion bugs API
• Recording which versions a bug affects
• Including upgrade guidance in a bug description

Use when the user says "review bugs", "/review-bugs", "pull new bugs", "what was reported in Bugs", "update the bug list", or asks for an auto-review of reported bugs. Pulls the new messages from the Voxt Bugs and Bugs (Mobile) chats, turns them into entries in docs/bugs.md, reconciles the list with GitHub issues, pull requests and dev commits, moves finished bugs to docs/bugs-closed.md, and lists what needs a human decision.

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

Automate Bugsnag operations through Rube MCP and Composio. The skill identifies available tools, reads their current input requirements, checks the service connection, and follows the discovered specifications to run supported tasks.

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

• Find tools for a Bugsnag task
• Check the service connection before running tasks
• Run supported operations in bulk

Automate Bugsnag operations through Rube MCP and Composio. The skill identifies available tools, reads their current input requirements, checks the service connection, and follows the discovered specifications to run supported tasks.

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

• Find tools for a Bugsnag task
• Check the service connection before running tasks
• Run supported operations in bulk

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 unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.

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

• Prioritizing open bugs at the start of a sprint
• Organizing new bugs after a team QA review
• Reviewing a backlog with more than ten open bugs

Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.

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

• Adding a Chromium bug to the documentation
• Recording WebKit or Firefox issues
• Checking reporter details and fix status before adding a row

Reproduce timing and ordering bugs in a CTF sandbox using controlled concurrent requests. Compare normal and racing runs, trace reads and writes, and preserve a minimal sequence that demonstrates duplicate actions or inconsistent state.

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

• Reproduce bugs triggered by simultaneous requests
• Investigate duplicate actions and ineffective duplicate prevention
• Trace stale reads and gaps in locking

Investigate bugs and slow applications through reproducible examples, logs, environment comparisons, and hypothesis testing. The skill structures root cause analysis and performance measurement, helping developers narrow down failures and verify that a fix works.

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

• Investigate bugs that occur only occasionally
• Measure and locate performance bottlenecks
• Collect evidence and reproduce production failures

Turn game bug descriptions or suspected code problems into structured reports with reproduction steps, severity, and priority. Follow reported bugs through fix verification and closure, recording test results or manual checks before marking an issue closed.

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

• Turning a bug description into a structured report
• Finding potential bugs in a specific file
• Verifying a fix through tests or manual checks

Prepare a game's launch day patch by selecting known bugs that are safe to fix quickly. Coordinate minimal fixes, verify affected areas, and document deferred issues, quality checks, rollback procedures, and patch notes.

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

• Selecting known bugs for a launch day patch
• Planning minor fixes from platform certification feedback
• Verifying fixes and checking affected game systems

Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.

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

• Testing encode/decode round trips across generated inputs
• Checking normalization and sorting properties
• Reviewing whether existing property tests assert meaningful rules

4人の異なる専門家ペルソナ（20年ベテランエンジニア、TDDエキスパート、Clean Codeエキスパート、バグハンター）で ソースコードを批判的にレビューするスキル。設計判断、テスト容易性、可読性、バグ検出の観点から コードの問題を検出し、改善提案を行う。Python/JavaScriptに対しては追加のチェックポイントを適用。 バグハンターは状態遷移、例外パス、依存関係、非同期競合に特化し、本番環境での問題を事前に検出する。 Use when reviewing source code from multiple expert perspectives to find design flaws, testability issues, code quality problems, and runtime bugs. Triggers: "critical code review", "multi-persona code review", "expert code review", "code quality assessment", "find bugs".

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

コードベースの規模に応じた目標値計算、倍増エスカレーション、領域追跡、最終検証を備えた体系的なバグスウィープ。/bugsweep 実行時や体系的なバグ調査が要求された場合に使用します。

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

재현하기 어려운 오류와 성능 저하를 증상 감지 테스트나 스크립트로 조사합니다. 원인 후보를 검증하고 수정한 뒤 재발 방지 테스트까지 확인합니다.

• 재현하기 어려운 오류 조사
• 처리 속도가 느려진 원인 조사
• 간헐적 오류를 반복해서 검증

코드 변경에서 버그, 보안, 예상 부하, 테스트 누락, 속도, 불필요한 구현을 점검합니다. 구체적인 문제 사례와 최소 수정안을 우선순위별로 보고합니다.

• 병합 전에 PR을 검토할 때
• 미커밋 변경의 버그와 위험을 확인할 때
• 위험한 로직의 테스트 누락을 찾을 때

브라우저, API, 명령줄 도구와 백그라운드 처리의 오류를 조사하고 수정·검증합니다. 세 단계의 점검 범위를 선택하고 수정 근거와 출시 판단 자료를 받습니다.

• 웹사이트 오류 수정
• API와 CLI 동작 확인
• 작업과 webhook 처리 확인

브라우저, API, 명령줄 도구와 백그라운드 처리의 오류를 조사하고 재현 절차와 근거를 담은 보고서를 작성합니다. 코드 수정 없이 조사와 보고에 집중합니다.

• 코드를 바꾸지 않고 오류 조사하기
• 재현 절차가 있는 오류 보고서 작성하기
• API와 백그라운드 처리 확인하기

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

Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.

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

• Investigate an issue from a Sentry URL or short ID
• Review unresolved issues and muted error reports
• Test noise filters and fixes for product bugs

Review code for security flaws, bugs, performance problems, maintainability, and test quality. Produce structured feedback with issue locations, likely impact, suggested fixes, positive observations, and a recommendation on whether changes are ready to merge.

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

• Reviewing a pull request before merging
• Investigating bugs and edge cases
• Checking security flaws and dependencies

Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.

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

• Setting up error monitoring for a new production app
• Investigating errors that monitoring fails to capture
• Reviewing critical alerts and on-call routing

Operate and test terminal apps without a display using named background sessions. Wait for visible screen changes, send keystrokes, reproduce Cline CLI bugs, capture text or PNG evidence, and write automated tests of interactive behavior.

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

• Reproducing Cline CLI interface bugs without a display
• Running an interactive process in the background
• Writing automated tests for terminal interactions

Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.

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

• Review uncommitted changes for bugs
• Check a pull request or branch before merging
• Find duplicated logic and unnecessary work