Results for “bugs”

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

The English summary is being prepared. Showing the original description.

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

The English summary is being prepared. Showing the original description.

Reproduce and debug "only happens in a DAW" audio plugin bugs (cutouts, glitches, parameter-change failures) entirely offline — headless Processor scenes for DSP bugs and a standalone AudioUnit host probe for adapter/host-interaction bugs. Use when a plugin misbehaves in Logic/Live/etc. but unit tests are green.

The English summary is being prepared. Showing the original description.

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

The English summary is being prepared. Showing the original description.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

The English summary is being prepared. Showing the original description.

Barrido sistemático de errores con un valor objetivo escalado a la base de código, escalado por duplicación, seguimiento de áreas y verificación final. Se utiliza al ejecutar /bugsweep o cuando el usuario solicita una revisión sistemática de errores.

The English summary is being prepared. Showing the original description.

系统化 Bug 扫荡工作流，包含基于代码库规模的目标值计算、翻倍升级机制、区域追踪及最终验证。适用于执行 /bugsweep 或用户要求进行系统化 Bug 排查时。

The English summary is being prepared. Showing the original description.

Систематический поиск багов с целевым значением, масштабируемым по размеру кодовой базы, удвоением при эскалации, отслеживанием областей и финальной верификацией. Используйте при вызове /bugsweep или по запросу систематической проверки кода.

The English summary is being prepared. Showing the original description.

Systematic bug sweep with a codebase-scaled target value, doubling escalation, area tracking, and final verification. Use on /bugsweep or whenever the user requests a systematic bug pass.

The English summary is being prepared. Showing the original description.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

The English summary is being prepared. Showing the original description.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

The English summary is being prepared. Showing the original description.

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

The English summary is being prepared. Showing the original description.

Run ongoing quality checks across OpenClaw subsystems, reproduce bugs, and verify fixes to their underlying causes. Track real environment tests, stress tests, independent reviews, and confirmed merges in an evidence report that supports resuming work.

• Investigate bugs across multiple OpenClaw subsystems
• Verify fixes through regression tests and independent review
• Check real provider, UI, and package behavior

Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.

• Building a feature one test at a time
• Fixing a bug with a failing test first
• Planning integration tests at agreed public interfaces

Inventory existing tests and identify gaps. Link requirements, business rules, risks, and bugs to stable test identifiers and executable evidence, maintaining a test registry that shows what is covered and what still needs verification.

• Inventory existing tests and identify gaps
• Link bug fixes to regression evidence
• Check client and server behavior against one shared contract

Verify Spring Boot changes through builds, static analysis that checks code without running it, tests, coverage checks, and security scans. Review the diff and produce a pass/fail report showing readiness and issues to fix.

• Checking a Spring Boot service before opening a pull request
• Verifying changes after refactoring or dependency upgrades
• Checking test coverage against the target

Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.

• Adding REST endpoints with tests first
• Reproducing bugs before fixing them
• Testing Apache Camel routes and event handling

Trace button clicks and form actions through each state change to uncover conflicting updates, unintended resets, and asynchronous timing problems. Report where the final screen behavior differs from what the user expects, with specific fixes.

• Investigating buttons that appear to do nothing
• Checking shared state after a major refactor
• Auditing critical user flows before release

Guides debugging through reproduction, comparison with working examples, hypothesis testing, and a focused fix. It starts with a repeatable check for the exact symptom and uses regression tests to verify the result.

• Investigating failing tests or builds
• Tracing faults across APIs, services, and databases
• Making intermittent bugs easier to reproduce

Review a codebase for bugs, security risks, failures under expected load, missing tests, slow paths, and unnecessary code. Receive prioritized findings with concrete failure cases, small proposed fixes, and the consequences of leaving each issue unresolved.

• Assess the quality of an inherited codebase
• Find risks under expected concurrent usage
• Identify unnecessary code and dependencies

Audit an entire code repository or a selected folder for bugs, security risks, load problems, missing tests, slow paths, and excess code. Get up to 20 prioritized findings explaining concrete problems, minimal fixes, and consequences.

• Assess the quality of an inherited codebase
• Find security and load risks across a project
• Identify code to delete, merge, or split

Fix iOS bugs by editing source code, rebuilding the app, deploying it again, and verifying the result on a real device. Preserve a state snapshot as test data to help detect recurrence.

• Fixing bugs reported by /ios-qa
• Verifying fixes after rebuilding and redeploying
• Preserving state snapshots for regression tests

Fix bugs and small behavior changes by tracing the cause and editing the smallest responsible part of the code. Preserve surrounding behavior and existing user changes, then run focused checks to confirm the fix and guard against recurrence.

• Fixing a bug without changing surrounding behavior
• Making a small, targeted behavior change
• Adding a test to prevent a specific bug from returning

Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.

• Capture screenshots to verify UI changes
• Read content rendered by JavaScript
• Reproduce UI bugs and record errors