testing
59
junit-fundamentals
Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.
TheBushidoCollective
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
59
creating-stories
Creates and modifies Storybook stories for Atomic components and sample pages. Uses MSW for API mocking, follows ui-kit conventions. Use when creating stories, adding component examples, building sample pages, or when user mentions Storybook, stories, or visual testing.
coveo
testing-security
testing
59
jest-configuration
Use when jest configuration, setup files, module resolution, and project organization for optimal testing environments.
TheBushidoCollective
testing-security
testing
59
playwright-test-architecture
Use when setting up Playwright test projects and organizing test suites with proper configuration and project structure.
TheBushidoCollective
testing-security
testing
59
cucumber-step-definitions
Writing effective step definitions and organizing test code
TheBushidoCollective
testing-security
testing
59
pytest-fixtures
Use when pytest fixtures, conftest files, parametrize decorators, and fixture scopes for comprehensive test setup.
TheBushidoCollective
testing-security
testing
59
cucumber-fundamentals
Core Cucumber concepts, Gherkin syntax, and feature file structure
TheBushidoCollective
testing-security
testing
59
vitest-testing-patterns
Use when vitest testing patterns including unit tests, mocks, spies, and browser mode testing.
TheBushidoCollective
testing-security
testing
59
cypress-advanced
Use when advanced Cypress features including custom commands, plugins, and network stubbing.
TheBushidoCollective
testing-security
testing
59
testng-fundamentals
Use when working with TestNG annotations, assertions, test lifecycle, and configuration for Java testing.
TheBushidoCollective
testing-security
code-quality
58
composewebview-code-review
Performs code quality checks and reviews for ComposeWebView. Validates expect/actual implementations, KDoc coverage, Spotless formatting, and multiplatform patterns. Use when reviewing PRs, checking code quality, or validating new features.
parkwoocheol
testing-security
security
58
ops-security-audit
Structured workflow for infrastructure security audits including compliance validation, vulnerability assessment, and security posture review.
LerianStudio
testing-security
testing
58
ringwriting-skills
TDD for process documentation - write test cases (pressure scenarios), watch baseline fail, write skill, iterate until bulletproof against rationalization.
LerianStudio
testing-security
testing
58
ringtesting-anti-patterns
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
LerianStudio
testing-security
testing
58
ringcondition-based-waiting
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
LerianStudio
testing-security
testing
58
ringtest-driven-development
RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.
LerianStudio
testing-security
testing
58
ringtesting-agents-with-subagents
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
LerianStudio
testing-security
code-quality
57
writer-selfloop
Writing self-loop for surveys: run the strict section-quality gate, then rewrite only the failing `sections/*.md` files until the report is PASS. **Trigger**: writer self-loop, quality gate loop, rewrite failing sections, expand thin sections, 自循环, 反复改到 PASS. **Use when**: per-section files under `sections/` exist, but the writing gate is FAIL/BLOCKED (missing/thin H3, out-of-scope citations, missing chapter leads). **Skip if**: you are still pre-C2 (NO PROSE), or evidence packs/anchor sheet are incomplete (fix C3/C4 first). **Network**: none. **Guardrail**: do not invent facts; only use citation keys present in `citations/ref.bib`; keep citations subsection- or chapter-scoped per `outline/evidence_bindings.jsonl`; H3 body files must not contain headings.
WILLOSCAR
testing-security
code-quality
57
dignified-python
Python coding standards with automatic version detection. Use when writing, reviewing, or refactoring Python to ensure adherence to LBYL exception handling patterns, modern type syntax (list[str], str | None), pathlib operations, ABC-based interfaces, absolute imports, and explicit error boundaries at CLI level. Also provides production-tested code smell patterns from Dagster Labs for API design, parameter complexity, and code organization. Essential for maintaining erk's dignified Python standards.
dagster-io
testing-security
testing
57
pipeline-auditor
Audit/regression checks for the evidence-first survey pipeline: citation health, per-section coverage, placeholder leakage, and template repetition. **Trigger**: auditor, audit, regression test, quality report, 审计, 回归测试. **Use when**: `output/DRAFT.md` exists and you want a deterministic PASS/FAIL report before LaTeX/PDF. **Skip if**: you are still changing retrieval/outline/evidence packs heavily (audit later). **Network**: none. **Guardrail**: do not change content; only analyze and report.
WILLOSCAR
testing-security
testing
57
exercise-builder
Add exercises to each tutorial module (inputs, expected outputs, verification steps) and update `outline/module_plan.yml`. **Trigger**: exercises, practice, verification checklist, 教程练习, 可验证作业. **Use when**: 已有模块计划（`outline/module_plan.yml`），需要为每个模块补齐至少 1 个可验证练习以形成 teaching loop。 **Skip if**: 还没有 module plan（先跑 `module-planner`）。 **Network**: none. **Guardrail**: 每个练习必须包含 expected output + verification steps；避免只给“思考题”无验收。
WILLOSCAR
testing-security
testing
57
fake-driven-testing
This skill should be used when writing tests, fixing bugs, adding features, or modifying the gateway layer. Use when you need guidance on testing architecture, working with fakes, implementing ABC gateway interfaces, or understanding the defense-in-depth testing strategy. Essential for maintaining test quality and understanding where different types of tests belong.
dagster-io
testing-security
code-quality
56
content-linter
Lint content for spelling errors, en-GB compliance, and writing quality. Use when checking markdown files before publication.
spences10
testing-security
testing
56
unity-test-runner
Execute and analyze Unity Test Framework tests from the command line. This skill automates test execution for Unity projects by detecting the Unity Editor, configuring test parameters (EditMode/PlayMode), running tests via CLI, parsing XML results, and generating detailed failure reports. Use this when running Unity tests, validating game logic, or debugging test failures.
Dev-GOM
testing-security