991 个 · 按相关度排序
Bug hunter. Reproduces bugs with failing tests (RED), then fixes with TDD. Accepts a prompt, issue URL, or bug description. Use when: bugfix, fix bug, debug, broken, regression, failing, doesn't work, fix this.
中文简介正在准备中。当前显示原文说明。
Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns.
中文简介正在准备中。当前显示原文说明。
Use when a diff may lack tests — missing assertions, uncovered branches, over-mocking, no regression test for a bug fix — dispatched by /review-changes, /do-and-judge, /judge, even without 'tests'.
中文简介正在准备中。当前显示原文说明。
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
中文简介正在准备中。当前显示原文说明。
[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes the issue.
中文简介正在准备中。当前显示原文说明。
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
中文简介正在准备中。当前显示原文说明。
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
中文简介正在准备中。当前显示原文说明。
Re-audit code changes to identify side effects, regression risks, and unhandled edge cases before merging or deploying. Use after a change is complete and before merging to a shared branch, before deploying a hotfix, after complex multi-module refactoring, or when a previous review may have missed side effects in async, state-mutating, or security-sensitive code paths.
中文简介正在准备中。当前显示原文说明。
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.
中文简介正在准备中。当前显示原文说明。
Implement minimal network events and component state with authority, conversion, dirtying, and regression coverage.
中文简介正在准备中。当前显示原文说明。
Reproduce failures, trace authoritative flow, prove the broken assumption, and add targeted regression coverage.
中文简介正在准备中。当前显示原文说明。
Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and layered automated + manual testing across all pages and user preferences.
中文简介正在准备中。当前显示原文说明。
Test or fix domain rules, state transitions, value objects, and domain services directly. Use for business-rule regression tests, rejected transitions, and model behavior without HTTP.
中文简介正在准备中。当前显示原文说明。
Test or debug application use cases through their public Action API, including persistence, authorization failures, atomic rollback, and post-commit reactions. Use when adding regression tests for business operations.
中文简介正在准备中。当前显示原文说明。
Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.
中文简介正在准备中。当前显示原文说明。
Virtual QA Lead that turns requirements into review-ready, TestRail-importable test cases in one conversation. Use it whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan, a checklist, test coverage, a regression suite, or a TestRail/Qase/Zephyr export, even without saying "test cases" ("write tests for this spec", "what should we check here?"). Especially useful when they attach their team's existing test cases to match. When the spec describes an API (endpoints, status codes, schemas, auth, OpenAPI/Swagger), Casely also builds a runnable Postman collection, so use it for "API tests", "Postman collection", or "tests I can run in Newman/CI". Triggers on the same request in any language.
中文简介正在准备中。当前显示原文说明。
Use when Invoice-Downloader work involves mailbox batch tests, truth audit, regression validation, P0/P1/P2 decisions, packaged frontend acceptance, or clean reruns.
中文简介正在准备中。当前显示原文说明。
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
中文简介正在准备中。当前显示原文说明。
Retest remediated findings, detect regressions, and generate remediation status and certification artifacts.
中文简介正在准备中。当前显示原文说明。
Use for deterministic terminal or CI browser automation, repeatable regressions, traces, snapshots, screenshots, and unattended playwright-cli batches. Route interactive or signed-in Chrome work through browser-automation-router first.
中文简介正在准备中。当前显示原文说明。
GStack review method for pre-landing code, diff, PR, or implementation review focused on bugs, regressions, missing tests, and release risks.
中文简介正在准备中。当前显示原文说明。
GStack investigation method for bugs, incidents, failing tests, regressions, and unclear behavior where evidence and root cause should precede fixes.
中文简介正在准备中。当前显示原文说明。
Runs a multi-phase quality audit of a codebase: derives behavioral requirements from code and docs, generates spec-traced tests, runs a three-pass code review and independent spec audits, and reconciles every bug with regression tests. Use for a deep quality assessment of a project, not a quick PR review.
中文简介正在准备中。当前显示原文说明。
Use when turning GitHub issues or bug reports into reproducible coding-agent repair loops with sandboxed execution, focused tests, patch generation, and regression verification.
中文简介正在准备中。当前显示原文说明。