测试与质量
3,371 个结果
- Openclaw Docker E2e AuthoringopenclawAuthor OpenClaw Docker E2E and live provider Docker lanes.
- Openclaw Qa TestingopenclawRun, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.
- Openclaw Test Heap LeaksopenclawInvestigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.
- Openclaw Test PerformanceopenclawBenchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.
- Openclaw TestingopenclawChoose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
- Prototype Openclaw TuiopenclawBuild throwaway, fixture-driven OpenClaw Clack or Pi TUI prototypes and compare multiple interactive variants side by side in tmux without running the full application or touching live state.
- Release Openclaw AnnouncementopenclawDraft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.
- Release Openclaw Plugin TestingopenclawPlan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.
- SpikeopenclawRun throwaway prototypes to validate feasibility, compare approaches, and report a verdict.
- Verify ReleaseopenclawVerify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release track.
- Finishing A Development BranchobraUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- Receiving Code ReviewobraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- Requesting Code ReviewobraUse when completing tasks, implementing major features, or before merging to verify work meets requirements
- Subagent Driven DevelopmentobraUse when executing implementation plans with independent tasks in the current session
- Systematic DebuggingobraUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- Test Driven DevelopmentobraUse when implementing any feature or bugfix, before writing implementation code
- Using Git WorktreesobraUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
- Verification Before CompletionobraUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- Writing SkillsobraUse when creating new skills, editing existing skills, or verifying skills work before deployment
- Codebase DesignmattpocockShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
- DiagnosemattpocockDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
- Grill With DocsmattpocockGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- GrillingmattpocockGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
- Improve Codebase ArchitecturemattpocockFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.