'defects' 검색 결과

Prepare selected pull requests for maintainer review by comparing failures with their current base, fixing authorized defects, and preserving contributor credit. Report complete or partial validation with evidence and outstanding checks before any separately authorized merge.

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

• Preparing selected pull requests before merging
• Distinguishing base failures from PR defects
• Fixing authorized defects while preserving contributor credit

Cleanup and triage of the task ledgers FOUND_DEFECTS.md, CURRENT_ERRORS.md, .matrx/AGENT_TASKS.md, .matrx/ARMAN_TASKS.md. Use when invoked as /task-hygiene <step>, cleaning up tasks, defects, or errors, triaging an error dump, promoting defects, or bootstrapping these files.

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

Investigate failed Agent QA runs using logs, recorded artifacts, and local source code. Make a focused code or test-definition repair, then verify the affected behavior while keeping product and infrastructure defects visible.

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

• Repair a failed staging test from recorded evidence
• Update an outdated Agent QA YAML definition
• Distinguish test failures from product or infrastructure defects

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

Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.

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

• Reviewing changes after editing code
• Checking a bug fix for further defects
• Reviewing code changes that add a feature

Diagnose and fix MSBuild property problems, including overwritten settings, ineffective conditions, and environment-dependent paths. Review defaults, list appending, and evaluation order so project files and shared build settings retain the intended values.

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

• Fix build settings overwritten by shared files
• Preserve existing compilation constants when adding new ones
• Correct conditions based on the target framework

Diagnose and fix concrete MSBuild property defects in projects and existing shared-file hierarchies. USE FOR: conditions, defaults, append versus overwrite, last-write-wins values, OS/TFM checks, portable paths, normalization, and reviews centered on those property defects. Property defects in Directory.Build.* remain in scope, including overwritten values across parent/child imports and conditions that run before TargetFramework is set, even when the fix changes import order or moves a property group to .targets. DO NOT USE FOR: placement-only or import-only requests with no concrete property defect, such as discovering shared files or choosing which file owns a target or customization (use directory-build-organization); item operations; target structure; broad reviews without a concrete property defect; non-MSBuild work.

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

REA의 CI와 테스트 모음을 조사하여 결함을 놓치는 판정과 테스트 데이터의 차이를 검증합니다. 필요한 검출 능력을 유지하면서 실측을 바탕으로 실행 비용도 검토합니다.

• 결함을 놓치는 CI 판정 조사
• 테스트 데이터와 현재 사양의 차이 확인
• 느린 테스트 모음의 불필요한 비용 측정

코드 변경 사항과 관련 테스트, 호출 지점을 읽기 전용으로 검토합니다. 변경으로 새로 발생한 수정 대상 결함을 찾아 근거, 심각도, 파일 위치와 함께 정리합니다.

• 커밋하지 않은 변경 사항 검토
• 병합 전 변경 사항 확인
• 특정 커밋에서 발생한 결함 조사

Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.

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

• Implement and verify a reproducible bug fix
• Submit an upstream Codex pull request
• Deliver a tested LazyCodex patch in an issue

Review a specified code change without editing files. Checks the full diff, surrounding code, tests, and callers to identify actionable defects introduced by the change, then reports findings by severity with file and line references.

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

• Review uncommitted changes for concrete defects
• Check changes that would merge into a base branch
• Review a specific commit and identify test gaps

Inspect 3MF files for 3D printing, detect cylindrical holes, and resize them to a chosen diameter. Repair mesh defects and compare files while preserving BambuStudio and PrusaSlicer metadata during file repacking.

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

• Finding cylindrical holes and checking their diameters
• Resizing selected holes to a specified diameter
• Repairing mesh defects before 3D printing

Review concrete code for exploitable security defects, including missing access checks, unsafe input handling, and exposed secrets. Report verified issues with file locations, reachable attack paths, severity, and suggested fixes.

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

• Review a code change for exploitable vulnerabilities
• Check authentication and access controls
• Trace unsafe input handling and secret exposure

Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.

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

• Documenting behavioral differences found during migration
• Organizing reproduction steps and test data
• Recording fixes, affected files, and validation steps

Review completed code changes for defects, security risks, unnecessary complexity, and missing tests. Findings are verified and reported with severity, file locations, and concrete failure scenarios, with separate assessments of standards and intended behavior for larger changes.

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

• Checking completed changes before release
• Reviewing compliance with documented development standards
• Checking implementation against ticket requirements

Test user journeys affected by a branch’s changes in a real browser. Check correctness and the experience for intended users, fix small defects with regression tests, and commit fixes alongside a report documenting results and unresolved decisions.

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

• Check user-facing changes before a PR is merged
• Test complete user journeys affected by a branch
• Fix small defects and add regression tests

Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.

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

• Review a production outage
• Investigate recurring defects
• Compare failing and working environments

Review a specified code change without editing files. Checks the full diff, surrounding code, tests, and callers to identify actionable defects introduced by the change, then reports findings by severity with file and line references.

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

• Review uncommitted changes for concrete defects
• Check changes that would merge into a base branch
• Review a specific commit and identify test gaps

Review OpenClaw frontend code and rendered screens for departures from Carapace design rules, accessibility issues, responsive defects, and inconsistent copy. Produce evidence-based JSON and Markdown reports that distinguish documented violations from judgment-based suggestions and guide narrowly scoped fixes.

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

• Check compliance with Carapace design rules
• Review desktop and mobile interfaces
• Audit accessibility and brand copy

Guide an approved defect fix from reproduction on current main through testing and independent validation. Record evidence for each operator workflow, track change size and rollback scope, and apply review records when receipt-driven development is enabled.

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

• Reproducing approved defects before implementation
• Recording runtime evidence for CLI and lifecycle flows
• Splitting fixes by cause and rollback scope

Review websites, apps, screenshots, or design code for redundant decoration, generic patterns, and usability defects. Receive prioritized findings tied to specific evidence, with removal or small corrections that preserve the interface’s existing design direction.

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

• Reviewing redundant decoration in a landing page
• Finding readability and usability issues in screenshots
• Prioritizing small fixes within the existing design

Review and refine websites and apps by finding generic decoration, inconsistent visual choices, and interface defects. Preserve the established art direction while improving hierarchy, layout, interaction states, and the connection between design choices and product needs.

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

• Removing unnecessary decoration from an existing page
• Keeping new components consistent with the design system
• Checking content hierarchy and primary actions

Review MSBuild project files and build definitions for correctness and maintainability. Get prioritized findings with concrete recommendations, distinguishing confirmed defects from conditional risks and valid exceptions such as F# source ordering or required imports.

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

• Reviewing build files for maintainability
• Checking path portability across operating systems
• Reviewing import safety and required-file assumptions

Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch. Seeds known defects into a copy of a real artifact plus a clean control, runs the checker, and reports recall and false-positive rate into a qualification ledger. Use when the user says "does this check work", "qualify the gate", "test my reviewer", "seed defects", "vaccinate", "qualify the checks", "can I trust this review", "does it pass for the right reason", or before relying on any automated check or referee simulation for a decision that matters. NOT a code fixer and NOT a reviewer itself — it grades the grader.

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