'defects' 검색 결과

Comprehensive adversarial audit of a theory, proof, math/econ paper, codebase, or set of claims — decompose into components, fan out independent skeptics that must return CONCRETE defects, adjudicate every finding with a separate judge, fix all confirmed defects, then re-verify. Use when correctness must be bulletproof and single-pass or round-by-round review is too slow and too shallow. Invoke for "audit this rigorously", "find ALL the bugs/gaps", "make this rock solid", "converge faster on correctness".

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

Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.

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

Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.

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

Triage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.

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

OpenClaw의 여러 Issue와 PR을 담당자별로 조사하고 수정·검증하며, 허용된 범위에서 병합과 해결된 항목의 종료까지 관리합니다.

• 여러 Issue와 PR의 수정을 관리합니다
• 기존 수정 PR을 마무리합니다
• 수정된 Issue를 검증하고 닫습니다

현재 소스와 테스트 결과를 바탕으로 OpenClaw 이슈와 풀 리퀘스트를 조사하고 검토합니다. 허용된 범위에서 수정부터 합병 완료 확인까지 진행합니다.

• OpenClaw 풀 리퀘스트 검토
• 보고된 버그를 로컬에서 수정
• 이미 해결된 이슈인지 확인

Kanban에서 구현 담당자가 넘긴 결과물을 독립적으로 검증합니다. 인수 조건과 테스트 증거를 대조해 승인, 수정 요청 또는 사람의 판단을 구하는 상위 전달을 기록합니다.

• 인수 조건에 따른 결과물 확인
• 수정 요청 후 다시 제출된 결과물 검토
• 재현 가능한 결함을 구현 담당자에게 전달

완성한 디자인을 배치, 요청 목적 충족, 브랜드 일관성, 접근성, 문구의 다섯 관점에서 점검하고 발견한 구체적인 문제를 수정합니다.

• 납품 전 디자인 점검
• 브랜드 지정 사항과의 일치 확인
• 키보드 조작과 명암 대비 확인

Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.

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

• Consolidating bug reports that share a root cause
• Turning an issue backlog into a repair roadmap
• Routing new bugs into existing plans

Evaluate whether tests catch defects in business logic, calculations, or state machines. Using Stryker, the skill introduces small code changes, reviews which changes escape detection, and helps strengthen tests where important behavior is insufficiently checked.

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

• Checking test quality beyond code coverage
• Introducing Stryker for a single module
• Strengthening tests for critical calculations

Review form validation so users, including people using screen readers, can understand and correct errors. Check field descriptions, required states, and grouped choices in rendered HTML, while accounting for React forms that handle submission in the browser.

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

• Make form errors understandable to screen reader users
• Check how required fields and grouped choices are marked
• Review validation in React forms

Review pull requests, branches, commit ranges, or local changes with GitNexus. Combine code relationship analysis with source and test inspection to identify concrete defects, missing tests, affected behavior, and risks before merging.

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

• Review a pull request before merging
• Trace regressions beyond changed files
• Find missing tests for changed behavior

Document bug fixes and incident recovery with a structured receipt covering the problem, cause, change, and verification evidence. Distinguishes verified results from partial or blocked work, identifies missing proof, and specifies the next check needed to close the gap.

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

• Record the evidence supporting a bug fix
• Report missing checks after a partial repair
• Document an incident blocked by an external condition

Review logs and source files from a completed manual example run. Check that results are current and complete, verify intended behavior beyond successful exit codes, and distinguish product defects from environment or credential problems.

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

• Review results after a manual example run
• Verify behavior in examples that exited successfully
• Separate product failures from environment problems

Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.

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

• Checking whether previous review findings were addressed
• Finding regressions introduced by follow-up commits
• Re-running tests against the current PR head

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

Find unused components, files, translation keys, and other unnecessary code across a codebase. Document every consumer and removal impact in a tracking issue, then turn one maintainer-approved candidate into a focused pull request.

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

• Periodically checking for accumulated unused code
• Finding orphaned translation keys
• Recording removal candidates and their impact in an issue

Review agent-written code changes before merge, focusing on concrete correctness defects. Uses independent subagent reviews, targeted verification, and fresh checks after substantial repairs, with a deeper evidence-based process for security, concurrency, persistence, or data-loss risks.

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

• Reviewing agent-written changes before merge
• Rechecking a substantial bug fix
• Examining security, concurrency, or data-loss risks

Review code changes or a repository for actionable bugs by tracing how components interact. Findings explain reachable triggers, incorrect behavior, consequences, and checked counterarguments. Correctness is the default focus; performance and security can also be selected.

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

• Reviewing changes for bugs before integration
• Investigating state mismatches across components
• Checking whether a fix introduces another defect

Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.

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

• Investigating failed PR checks
• Separating intermittent test failures from code defects
• Checking whether the base branch already fails

Investigate Convex production errors, prepare fixes on a branch, and verify them before opening a pull request for human review. After an approved deployment, check whether the same error recurs. Never automatically merge changes or deploy to production.

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

• Investigating recurring production errors
• Preparing verified fixes for code or schema defects
• Checking data changes against a production snapshot

Coordinate AI agents to create short videos, from copy and storyboards to images, narration, subtitles, and MP4 assembly. The workflow includes quality checks, revision requests, and production data reviews to guide later improvements.

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

• Creating a 30-second product introduction video
• Coordinating agents across video production tasks
• Checking images and audio sync before delivery

Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.

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

• Start implementation from the assigned user outcome
• Reproduce a defect and verify its repair
• Review delivered behavior against requirements

Investigate failed CircleCI jobs, identify the first meaningful error, and distinguish reproducible defects from temporary failures. Apply focused fixes to configuration, test setup, or build code, then explain validation criteria and remaining uncertainty.

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

• Investigate a failed CircleCI job
• Classify intermittent pipeline failures
• Fix configuration or build environment issues