938 skills · sorted by relevance
Review code changed during a project phase for bugs, security vulnerabilities, and quality issues. Choose the review depth or specific files, receive findings grouped by severity, and optionally apply fixes followed by another review.
Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.