Testing & QA
3,371 results
- Drawio SkillAgents365-aiCreate and edit draw.io/diagrams.net diagrams as editable `.drawio` files. Covers architecture, UML/ERD/sequence, BPMN, network, and swimlane views authored from a description or converted from code, IaC, SQL, and API schemas, plus sync, query, test, review, export, and publish of existing diagrams.
- Tests MaintenanceJetBrainsMaintains IdeaVim test suite quality. Reviews disabled tests, ensures Neovim annotations are documented, and improves test readability. Use for periodic test maintenance.
- ibelick/ui-skillsJulien ThibeautCollectionSkills for Design Engineers
- Axum Test TransportFastreplChoose between in-process `tower::ServiceExt::oneshot` tests and real `tokio::net::TcpListener` server tests for Axum services in this repository.
- Qa Cli MCP APIFastreplSelect and run explicitly requested, risk-based QA for Anarlog's CLI, webhooks, stdio MCP, hosted Cloud API, and remote MCP. Test only affected lanes unless comprehensive coverage is requested.
- Qa Critical UXFastreplQA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
- Qa Critical UXFastreplQA the critical Pro user journey before a desktop release — onboards from scratch, launches without hanging, captures microphone and system audio, produces an automated summary, and restores the note from cloud sync. Use before cutting a stable release or when asked to QA the app.
- Qa Critical UXFastreplQA Anarlog's critical Pro user journey when explicitly asked — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
- Release CliFastreplReview Anarlog CLI and agent-access coverage, validate shared agent packages, and verify the CLI shipped in each desktop artifact and install path.
- TestingFastreplUse when adding, changing, deleting, or reviewing tests in Anarlog (TypeScript, Rust, or node --test scripts), deciding whether a change needs a test, fixing a failing test, or pruning test suites. Covers what is worth testing, what to leave untested, test budgets, and the test-weight report.
- Testing Android CodebitwardenThis skill should be used when writing or reviewing tests for Android code in Bitwarden. Triggered by "BaseViewModelTest", "BitwardenComposeTest", "BaseServiceTest", "stateEventFlow", "bufferedMutableSharedFlow", "FakeDispatcherManager", "expectNoEvents", "assertCoroutineThrows", "createMockCipher", "createMockSend", "asSuccess", "Why is my Bitwarden test failing?", or testing questions about…
- Benchmark WorkflowXberg.ioRun, diagnose, or change Xberg extraction benchmarks, quality scoring, benchmark fixtures, artifact contracts, and independently sourced ground truth. Load for the Benchmarks workflow or benchmark-harness work, not ordinary unit tests.
- Test CorpusXberg.ioThe test_documents submodule is a bucket-fetched fixture corpus that is not committed. This skill covers read_test_fixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing missing-fixture failures.
- Browser SkillTencentAutomate the user's logged-in Chromium through this plugin's injected bsk_* tools. Use to read pages, fill forms, operate tabs, inspect page activity, debug a website, or test a UI.
- Browser SkillTencentAutomate the user's logged-in Chromium browser: read pages, fill forms, scrape data, operate tabs, test a UI, or debug a website. Requires the bsk CLI and browser extension.
- HonoopenstatushqEfficiently develop Hono applications using Hono CLI. Supports documentation search, API reference lookup, request testing, and bundle optimization.
- Testing SetupandroidAnalyze and create a testing strategy for Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.
- Repo Source Code Reviewopen-circleReview pull requests and source code changes in /library/src/. Use when reviewing PRs, validating implementation patterns, or checking code quality before merging. Covers code quality checks, type safety, documentation review, test coverage, and common issues to watch for.
- Repo Structure Navigateopen-circleNavigate the Valibot repository structure. Use when looking for files, understanding the codebase layout, finding schema/action/method implementations, locating tests, API docs, or guide pages. Covers monorepo layout, library architecture, file naming conventions, and quick lookups.
- No MistakeskunchenguidValidate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
- Game Automationrehan-remadeLaunch, see and drive a real game so an agent can test its own mods. Covers launching via Steam or the exe, windowed mode at a fixed size, screenshots of the game window (GPU-safe capture), clicking and typing into menus, holding keys, relative mouse, crash-reporter cleanup, killing by PID, reading logs, scripted test scenes, and an in-game JSON bridge that lets an agent observe and act.
- Product Feature Tech Designdigoal将 PRD 翻译成「可独立测试」的功能设计文档。文档的下游使用者包括开发者、评审者、测试者,且三方互相隔离(测试者看不到开发者写的代码),所以必须把行为、状态、接口、数据、权限、异常、验收标准全部显式化,让测试者能独立从文档推导用例。输入是一份已写好的 PRD 文档,输出是一份完整的 Markdown 功能设计文档,保存到当前项目的 `markdown/` 目录。适用于:写功能设计文档、技术设计文档、Tech Design、详细设计说明书、FDD、Functional Design Doc、Detailed Design、模块设计文档、把 PRD 翻译成开发设计、把需求拆成可开发/可测试/可评审的规格。
- Product Feature Tech Designdigoal输入 PRD 文档（Markdown 或 PDF），以开发架构师的角色编写字段/接口级精度的功能设计文档（Functional/Technical Design Doc），以 Markdown 格式保存到当前项目 markdown/ 目录。这份文档是开发者、reviewer、测试者三方协作的唯一契约——三者互相隔离、不能看对方的产出物（测试者看不到代码，reviewer 不参与开发），所以必须把每个功能点写到可直接落地、可直接测试的精度：接口请求/响应字段、错误码、状态机、数据模型、异常边界场景都要明确。
- Product Feature Tech Implementdigoal基于功能设计文档与现有源码，端到端实现一个产品功能：开发、代码 review、测试用例编写与执行， 循环迭代直到测试通过，最终产出用户手册与实现总结文档（保存到当前项目 markdown/ 目录）。 触发条件：用户提供了功能设计文档（PRD/设计文档/需求描述）+ 源码目录（或代码库路径）， 并希望"实现这个功能"、"开发这个功能"、"把这个设计文档变成代码"、"做这个功能的开发+测试"、 "完整实现并测试"、"端到端开发"，或明确要求按"开发-review-测试"循环推进直到测试通过。 也适用于需要额外运行环境的开发任务，例如 PostgreSQL/MySQL 等数据库插件开发 （可能需要编译、搭建实例、配置参数、初始化、跑测试）、需要启动服务进程才能测试的后端功能、 需要特定运行时环境的库或框架功能。