GitHub
proof-of-work
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
☆ 0View skill
data ai testing AI Skills
Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Categories: data ai testing
data ai testing Clear filters
Browse skills
GitHub
pytest-fixtures
Use when pytest fixtures, conftest files, parametrize decorators, and fixture scopes for comprehensive test setup.
☆ 0View skill
GitHub
pytest-plugins
Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.
☆ 0View skill
GitHub
pytest-advanced
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
☆ 0View skill
GitHub
test-review-skill
Use to review test coverage for completeness and quality
☆ 0View skill
GitHub
qa-destroyer
QA & Edge-Case Destroyer that kills weird bugs before users see them. Use when testing, reviewing edge cases, or hunting for bugs.
☆ 0View skill
GitHub
ralph
Spec-driven development with task-by-task execution. Transforms feature ideas into structured specs (research, requirements, design, tasks) then executes them autonomously with fresh context per task. Supports...
☆ 0View skill
GitHub
playwright
Browser automation using Playwright (Firefox, Chromium, WebKit). Supports ARM64 where Chrome doesn't work. Provides page navigation, content extraction, screenshots, and interactive actions.
☆ 0View skill
GitHub
test-thinking
Lightweight reference for designing meaningful test variations.
☆ 0View skill
GitHub
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or es...
☆ 0View skill
GitHub
running-tests
Executes Unity tests and checks coverage. MUST use proactively after implementing features, fixing bugs, or modifying Domain/Application layer code. Also triggers on "test", "テスト".
☆ 0View skill
GitHub
test-designer
从 Spec 提取验收标准，生成测试计划文档。当用户说"设计测试"、"测试计划"时自动触发。
☆ 0View skill
GitHub
test-reporter
解析测试结果，生成结构化测试报告。当用户说"测试报告"、"生成报告"时自动触发。
☆ 0View skill
GitHub
test-generator
根据测试计划、leaf Spec 或 design.md 自动生成测试用例。当用户说"生成测试"、"写测试"时自动触发。
☆ 0View skill
GitHub
reactut
on unit test creation in a react native proyects
☆ 0View skill
GitHub
deliver-feature
Automated delivery pipeline: Static Check -> Logic Test -> Smoke Test -> Deploy.
☆ 0View skill
GitHub
chrome-extension-development
Use when building Chrome extensions (Manifest V3). Covers floating panel architecture, sidepanel API, storage patterns, message passing, content scripts, SPA navigation detection, context menus, Vitest testing,...
☆ 0View skill
GitHub
browser-automation
Use when automating browsers with Playwright/Puppeteer, testing Chrome extensions, using Chrome DevTools Protocol (CDP), handling dynamic content/SPAs, or debugging automation issues
☆ 0View skill
GitHub
ios-dev
Methods for working with the ios simulator, mcp, and maestro test framework
☆ 0View skill
GitHub
ui-check
Use Playwright MCP to check UI styles and usability. Automatically used for requests like "check UI", "verify appearance", "take screenshot", "UI review", "screenshot analysis".
☆ 0View skill
GitHub
test-generation
Generates comprehensive Elixir tests using ExUnit following TDD principles.
☆ 0View skill
GitHub
mcp-browser-verify
Use browser automation MCP (Playwright/Browser/Browser-Use) to validate UI flows, capture screenshots, and reproduce issues. Use when visual verification or web flow testing is needed.
☆ 0View skill
GitHub
troubleshooting-rca
Perform root-cause analysis for bugs/errors/regressions using logs, repro steps, and hypothesis testing. Use when the user reports “nie działa”, stack traces, failing tests, or regressions.
☆ 0View skill
GitHub
test-generation
Generate comprehensive test cases for code
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.