ai-bouncer E2E 테스트 실행. install, uninstall, update, hook 동작을 자동 검증. 사용자가 "테스트 돌려", "e2e 실행", "설치 검증", "bouncer 테스트" 등을 요청하면 이 스킬 사용. ai-bouncer 변경 후 검증이 필요한 모든 상황에서 사용할 것.
Pont entre les Acceptance Scenarios SpecKit et Playwright Agents. Convertit les AS de spec.md en specs Markdown compatibles Planner, lance le Generator, et vérifie la traçabilité…
Run browser tests on pages affected by current PR or branch — from marcusrbrown/systematic
Use when the user wants comprehensive user-facing end-to-end test scenarios for a feature description.
Use BEFORE writing any test — enumerate cases per behavior (happy / boundary / error / abuse), prioritize by likelihood × impact, cross-check via subagent — even if the user just…
Create or update project test-case assets and test reports. Use when Codex is asked to generate test cases in Excel, produce a Word/DOCX test report, summarize automated test…
Use when the user wants a decision-tree style test case design with inherited setup and per-leaf assertions.
Create integration and end-to-end test scenarios covering workflows, API interactions, database operations, and system boundaries. Use when testing.
Design or implement behavior-focused tests for software changes across languages and frameworks. Use for test strategy, regression coverage, or writing tests; do not change…
Produce a hand-runnable human test checklist alongside automated tests. Run after writing automated test suites for a phase/feature that ships user-visible behavior.
Use when writing, reviewing, or debugging Apex test classes, test data factories, async test behavior, negative-path assertions, or callout mocking.
Run staged evaluations against a Claude Code plugin to verify that skills, agents, commands, hooks, and MCP components trigger when they should.
Run the Weave router locally in docker compose and drive it with `claude -p` to reproduce and verify routing/translation behavior for a specific upstream model (e.g.
Produce the closure report that wraps up a test cycle. Use when a lead says "write the test closure report", "summarize the test cycle", or needs an end-of-cycle summary for…
Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings.
함수·클래스·모듈에 대한 테스트 작성을 요청하거나, "테스트 만들어줘", "unit test", "테스트 코드", "test case 작성" 표현이 있을 때 활성화됩니다. 수행 내용: 대상 코드를 분석해 Given-When-Then 패턴 기반의 단위 테스트를 자동 생성합니다.
Use when you need to audit whether tests are complete for a project or PR — checks good case, bad case, boundary cases, 100% coverage, unit/integration/e2e test layers, then…
Generate protocol/interface test suites that any implementation must pass. Define the contract once, test every implementation.
The test_documents submodule — a bucket-fetched fixture corpus that is not committed, the read_test_fixture helper that keeps a missing fixture out of the build, why a git…
Analyze and improve test coverage. Use when reviewing coverage gaps, writing missing tests, setting up coverage tooling, or improving branch/line/statement coverage for any…
Reviews test coverage and suggests missing test cases for error paths, edge cases, and business logic. Activates when users write tests or implement new features.
Analyzes test coverage gaps and suggests test cases for untested code paths. Use when user requests test improvements, coverage analysis, or wants to increase test coverage.
Evaluate test completeness using the 8 dimensions framework. Use when: writing tests, reviewing test coverage, ensuring test quality.
Establishes a committed test coverage baseline and CI gate on the module being migrated — before any migration skill runs — so regressions are detectable.
Identify untested code paths, uncovered branches, and missing test scenarios using coverage analysis, risk mapping, and change-based coverage tracking
Analyze test coverage, identify gaps, detect dead code, and improve test quality. Use when user asks to check coverage, review tests, find untested code, or improve test…
Analyze test coverage gaps and generate tests to improve coverage. Use when improving test coverage, finding untested code, or writing missing tests.
Optimizing test coverage beyond line coverage including branch coverage, mutation score, path coverage, and identifying meaningful coverage gaps.
Use when reasoning about code coverage as a strategic measurement rather than a target: the coverage-criterion hierarchy (function, statement, line, branch, decision, condition,…
Test data management patterns: factory functions, fixtures, database seeders, test isolation strategies, and safely anonymizing production data for testing.
Anonymizing production data for testing while maintaining referential integrity, data distributions, and edge case representation.
Test Data Builder - Auto-activating skill for Test Automation. Triggers on: test data builder, test data builder Part of the Test Automation skill category.
Construct test objects through builders and factories with valid defaults so each test states only the fields it cares about.
Generates realistic, maintainable test data with factories instead of brittle shared fixtures — factory libraries (Ruby factory_bot, Python factory_boy/model-bakery, PHP…
Generate test fixture factories for your models. Builder pattern and static factories for zero-boilerplate test data. Use when tests need sample data setup.
Use when designing or building reusable Apex test data factories: @IsTest utility classes, SObject hierarchy construction, bulk data generation, portal user factories with…
Synthetic test data generation and management using Faker.js and similar tools. Generate realistic test data, create data factories, implement database seeding, and manage test…
Use to plan test data — factories over fixtures, per-test isolation, deterministic personas (users, roles, tenants) for authorization tests, and strict separation from production…
Post-execution skill for the test-readiness pipeline. Computes a corrective-commit ratio per milestone from git log to surface over-specified or under-specified tasks.
Quantify and prioritize test technical debt by analyzing coverage gaps, flaky test ratios, outdated assertions, and missing test categories across codebases.
Use to PRODUCE test-suite artifacts — author a new test or test plan for a feature, shape a cross-layer test strategy (what to test at which layer, as a portfolio), or plan which…
Use this agent when you need to evaluate test quality using Dave Farley's 8 properties of good tests.
Wizualne testowanie designow - ustawia kazdy design, odpala nagrywanie, robi screenshot i ocenia wyglad
Use when testing the Hubble Electron desktop app, especially when inspecting, clicking, screenshotting, or verifying a real note edit in the running app.
Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others.
Automatically detect test frameworks (Jest, pytest, RSpec, xUnit) in projects by analyzing configuration files and dependencies
Analyze, prioritize, and document test cases in TMS (Jira/Xray) -- the bridge between manual QA and test automation.
Run a repeatable docs-site check that builds locally, opens the site across device sizes, and reports layout, accessibility, and interaction issues.
Choose stubs, fakes, and mocks deliberately and default to verifying state over interaction so tests survive refactors.
Use when designing or reviewing test doubles — the stand-in objects that replace real collaborators in a test: the five-kind taxonomy (dummy, stub, spy, fake, mock) from…
Comprehensive guide to test doubles including mocks, stubs, spies, fakes, and dummies with when-to-use guidelines and anti-pattern avoidance.
Test-Driven Development (TDD) - design tests from requirements, then execute RED -> GREEN -> REFACTOR cycle.
Test-driven bug-fix methodology — reproduce the defect first, write a failing test that captures it, then fix red-to-green. Load when fixing a bug, defect, or regression report.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks…
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior.
Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually — from…
Enforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually — from…
Execute feature work and bug fixes with a tracer-bullet red-green-refactor loop. Use when building behavior that should be guided by tests, when fixing regressions, or when the…