'fix' 검색 결과

Investigate errors, failing tests, or slow behavior and explain the causal chain with source file and line references. Deliver diagnosis alone or apply a verified fix, starting with a test that reproduces the defect.

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

• Trace the cause of an error or failing test
• Investigate unexpectedly slow behavior
• Get a diagnosis before deciding on a fix

Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.

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

• Continuously monitor automatic test failures on main
• Coordinate repair ownership across maintainers
• Review peer fixes and assess merge readiness

Check mathematical proofs in LaTeX with review by a separate AI model. Identify missing assumptions and unsupported steps, explore counterexamples, repair derivations, and keep an audit record of issues, changes, and follow-up reviews.

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

• Checking proofs in a theory paper
• Finding missing assumptions in lemmas
• Repairing gaps in mathematical derivations

Improve research code, results, and paper drafts through repeated review by a second Codex agent. The workflow implements fixes, checks them again, and records assessments and unresolved issues across up to four rounds.

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

• Improve research before submitting a paper
• Repeat fixes and reviews of experimental results
• Track unresolved concerns across review rounds

Iteratively improve research by having Claude Code review code, results, and drafts while Codex implements fixes. Repeat until the assessment meets the stopping criteria or the round limit is reached, preserving feedback and unresolved issues.

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

• Repeating research reviews and fixes before submission
• Checking whether claims match code and experiment results
• Tracking how reviewer concerns are addressed across rounds

Run repeated reviews of research work, implement fixes, and request another assessment for up to four rounds by default. The workflow records progress and stops when both the review score and verdict meet its acceptance rules.

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

• Revising research work through repeated reviews
• Keeping a record of review findings and fixes
• Resuming an interrupted review process

Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.

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

• Implementing an approved security remediation plan
• Rechecking a reviewed fix against current code
• Adding regression tests for a security boundary

Diagnoses and fixes Java style violations in the FE module using Checkstyle, a tool that checks coding rules. It interprets errors, applies the project's formatting and import restrictions, and reruns checks to verify fixes.

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

• Checking FE Java changes before committing
• Fixing build failures caused by Checkstyle violations
• Understanding project-specific style and import rules

Review an existing bug-fix pull request using validated reproduction tests and the complete code diff. Assess root-cause coverage, scope, and regressions, then document behavioral evidence and follow the workflow's branch and approval rules.

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

• Independently verifying an existing bug-fix pull request
• Checking a complete diff for scope and root-cause coverage
• Recording the user journey on the proposed fix

Review code changes with an independent agent from a different model provider. After tests pass, check a fixed diff against acceptance criteria, send blocking issues back to the implementer, and repeat until review passes.

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

• Get an independent review from another model provider
• Check a pull request against acceptance criteria
• Turn blocking findings into concrete fix tasks

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

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

• Reproducing a first-run setup problem
• Inspecting menus in a narrow terminal
• Checking help text and command visibility

Investigate a reported bug before choosing a fix. Trace the actual failure, test competing explanations, and examine design history so the proposed change preserves intended behavior and clearly separates verified findings from unresolved assumptions.

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

• Reconstructing the conditions of a reported bug
• Distinguishing a symptom from its underlying cause
• Checking intended behavior in tests and history

Analyze bug-fix commits in a Git repository to uncover recurring failure patterns. Produce individual bug analyses and a reusable pattern guide that removes project-specific details, helping inform future code reviews.

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

• Extract recurring bug patterns from past fixes
• Build a reusable guide for code reviews
• Analyze fixes within a chosen date range or path

Combine Convex authorization, code quality, performance, and failure audits into one readiness report. It removes duplicate findings, scores confirmed issues with a stated formula, and orders the fixes while clearly identifying checks that could not run.

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

• Reviewing a Convex app before launch
• Combining audit findings into one report
• Prioritizing authorization and performance fixes

Review and fix interface accessibility against WCAG 2.2, a web accessibility standard. Check keyboard navigation, focus, screen reader labels, forms, motion, and zoom, then report failures with their criteria and implement fixes using the project's existing styling system.

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

• Check flows using only the keyboard
• Fix control names and screen reader announcements
• Improve form labels and error feedback

Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.

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

• Grouping accumulated bug reports by root cause
• Planning one fix for several related issues
• Checking test evidence before closing issues

Run two independent reviewers against the same fixed target, then compare their findings. With approval, address severe issues confirmed by both and reassess the fixes, using at most two correction rounds before a final verdict.

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

• Request two independent reviews of a specific target
• Separate confirmed issues from disputed findings
• Fix severe issues confirmed by both reviewers

Validate security patches by comparing vulnerable and patched code against exploit tests, related attack variants, and normal behavior. Produce reproducible logs showing remaining flaws, regressions, newly introduced security failures, and gaps that still need testing.

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

• Validate an AI-generated security patch before review
• Check related attack variants for incomplete fixes
• Check whether a fix breaks normal behavior

Evaluate local Codex skills and plugins, understand their scores, and identify fixes to prioritize. Get explanations of token estimates, set up benchmark scenarios, and prepare workflows for measuring actual token usage.

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

• Evaluate a local skill or plugin
• Understand scores and prioritize fixes
• Explain token estimates and prepare actual measurements

Improve an evaluated Codex skill by turning plugin-eval findings into prioritized changes. Refine activation descriptions, shorten SKILL.md, move lengthy details into supporting files, fix structural issues, and compare evaluation results before and after the rewrite.

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

• Prioritizing fixes after a skill evaluation
• Shortening SKILL.md and reducing token use
• Clarifying when a skill should activate

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

Investigate unfamiliar codebases before fixing bugs, adding features, or refactoring. Follow relevant code paths, plan focused changes, and verify results, while recording useful discoveries in .notebook/ so later sessions can build on earlier investigation.

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

• Investigate and fix bugs in unfamiliar code
• Add features following existing project conventions
• Trace and document authentication or other flows

Collect review threads and comments from the open GitHub pull request for the current branch. Summarize the fixes each comment needs, then apply changes for the comments the user selects using the gh command-line tool.

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

• Reviewing outstanding pull request feedback
• Choosing which review comments to address
• Applying fixes for selected comments

Investigate bugs by tracing symptoms through code and recent changes, reproducing failures, and testing a specific cause before fixing it. Produce a focused correction, a regression test to catch recurrence, and an evidence-based debugging report.

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

• Investigate errors that keep returning after fixes
• Trace a regression through recent changes
• Analyze failures that occur only in certain environments