'bugs' 검색 결과

Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.

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

• Investigate production outages and rising error rates
• Trace causes using logs, metrics, and code
• Reproduce bugs and validate minimal fixes

Run OpenClaw tests and reproduce bugs on remote machines through Crabbox. Choose a suitable execution provider, verify realistic user workflows, and report the actual provider, environment ID, logs, and timing.

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

• Run broad OpenClaw tests in a remote CI environment
• Reproduce installation or Docker bugs
• Verify behavior on macOS, Windows, or WSL2

Investigate independent bugs or test failures concurrently by assigning each problem area to a separate agent. Define clear boundaries and expected reports, then review the fixes, check for conflicts, and run the full test suite before integration.

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

• Investigate unrelated test failures in parallel
• Split independent subsystem bugs among agents
• Write focused assignments with clear boundaries

Investigate bugs, failing tests, and unexpected behavior through reproducible steps, logs, and comparisons with working code. Follow four stages to identify the root cause, test a hypothesis, apply a focused fix, and verify the result.

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

• Investigating failing tests
• Tracing production bugs to their source
• Finding where a build or integration breaks

Explore a web application as a user to find bugs and usability problems. Produce a structured report with reproducible steps, screenshots, and videos for interaction issues, giving responsible teams clear evidence to investigate.

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

• Checking core workflows before release
• Finding usability problems in forms and navigation
• Preparing bug reports with reproduction evidence

Investigate bugs, failed tests, and unexpected behavior through reproducible steps, evidence gathering, and comparison with working code. Test one hypothesis at a time, then implement a focused fix and verify it with tests.

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

• Investigating failed tests or builds
• Tracing production bugs across components
• Reassessing a problem after repeated failed fixes

Verify a reported security bug by tracing inputs, checking attacker capabilities, and examining existing protections. Produces a documented TRUE POSITIVE or FALSE POSITIVE verdict for each finding, with deeper verification for complex cases.

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

• Checking whether a reported vulnerability is real
• Verifying the conditions needed to exploit a finding
• Reviewing suspected false positives

Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.

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

• Reproducing and fixing broken UI interactions
• Checking desktop and mobile layouts
• Investigating blank pages and console errors

Review Python changes against shared team standards to find bugs, missing regression tests, and security issues. Findings are ordered by severity and include file names and line numbers so reviewers can locate each problem.

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

• Reviewing Python changes before merging
• Checking that bug fixes include regression tests
• Finding unsafe SQL and exposed secrets

Plan substantial DeepChat changes with a written design proposal and a clear implementation path. Record decisions, track progress, review the completed change, and select focused validation for features, complex bugs, or architecture updates.

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

• Planning a substantial new feature
• Recording the diagnosis and fix for a complex bug
• Documenting architecture changes or migrations

Test a web application using branch changes, selected pages, or the whole app as scope. Choose among three testing levels, document issues with evidence, fix them in separate commits, and verify results in a release-readiness report.

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

• Checking changed pages before opening a pull request
• Running a quick check for major bugs before committing
• Reviewing a release candidate for visual and functional issues

Audit a Claude Code installation for the cache issues documented in this skill. Check versions, configuration files, session resume usage, and installed binaries, then report exposure, suggested actions, and informational limits on tool result retention.

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

• Investigate cache behavior and unexpected costs
• Check session resume usage in settings and scripts
• Find outdated Claude Code binaries

Investigate bugs and failing tests through four stages: finding the root cause, comparing working patterns, testing a hypothesis, and implementing a fix. Uses reproduction steps, diagnostic evidence, and regression tests to check the result.

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

• Tracing the cause of a failing test
• Following runtime errors back to invalid data
• Finding the change that broke working code

Set up a consistent local environment for developing ClawTeam, then validate changes with focused tests and real agent workflows. Includes scripts for connecting other projects to local skills and guidance for investigating coordination bugs.

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

• Set up a consistent local development command
• Reproduce worker startup or messaging bugs
• Validate agent coordination after code changes

Advance one development task by managing an existing pull request, fixing a build failure or bug, or implementing a queued idea. Record the work and integrate changes into auto-dev only after automated checks pass.

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

• Implementing one queued idea
• Continuing work on an open pull request
• Fixing failed checks or reported bugs

Run OpenClaw tests and reproduce bugs on remote machines through Crabbox. Choose a suitable execution provider, verify realistic user workflows, and report the actual provider, environment ID, logs, and timing.

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

• Run broad OpenClaw tests in a remote CI environment
• Reproduce installation or Docker bugs
• Verify behavior on macOS, Windows, or WSL2

Review completed code through three roles: a critical reviewer, a verifier, and an adjudicator. Check evidence, look for bugs introduced by fixes, and produce an actionable repair list with regression tests and traceable review reports.

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

• Reviewing code before a release
• Checking major refactors for regressions
• Verifying that reported fixes actually work

Develop features, fix bugs, and refactor code by writing tests before implementation. The workflow combines unit, integration, and end-to-end tests of complete user flows, with an 80% coverage requirement and checks for errors and boundary cases.

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

• Build a new feature from user journeys
• Write a test that reproduces a bug before fixing it
• Refactor existing code while keeping tests passing

Operate, diagnose, and test the live All API Hub extension interface on desktop or supported Android browsers. Use logged-in sessions to reproduce bugs, verify account workflows, and check development updates through browser debugging connections.

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

• Reproducing extension UI bugs in a logged-in session
• Diagnosing an installed Android release
• Checking extension changes with hot updates

Investigate bugs in a running local application using service logs, traces that follow requests across services, and a shared browser. Connect frontend actions to backend activity, inspect failures, and verify that tracing records appear as expected.

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

• Investigating bugs in a running local service
• Following a request across multiple services
• Reproducing frontend issues in a shared browser

Build features or fix bugs through test-driven development: write one failing test, add enough code to pass, then refactor. Focuses on observable behavior through public interfaces, helping tests remain useful when internal code changes.

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

• Building a feature one tested behavior at a time
• Reproducing a bug with a failing test before fixing it
• Designing integration tests around public interfaces

Audit an existing app verification skill against source code and the running application. Update outdated instructions, feature maps, and test helpers using evidence, while reporting product bugs and blocked checks separately.

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

• Refresh verification steps after app changes
• Find missing features in a verification map
• Repair helpers that cannot run valid checks

Explore open-ended design, architecture, and naming decisions through parallel agents with different perspectives. The skill groups and scores ideas, flags hidden traps, and develops promising options with concrete first steps and key risks.

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

• Comparing architecture options
• Exploring product or API names
• Investigating bugs with an unclear cause

Keep a persistent record of project bugs and blockers in a local Markdown file. List issues by severity and category, inspect individual records, and save resolution notes so problems and their fixes remain available across sessions.

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

• Recording a bug to address later
• Reviewing unresolved issues across sessions
• Saving resolution notes after a fix