Testing
Unit tests, integration tests, test automation
ring:dev-frontend-visual
by LerianStudio
Gate 4 of frontend development cycle - ensures all components have snapshot tests covering all states, viewports, and edge cases.
ring:condition-based-waiting
by LerianStudio
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
ring:testing-anti-patterns
by LerianStudio
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
ring:dispatching-parallel-agents
by LerianStudio
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
ring:testing-agents-with-subagents
by LerianStudio
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
ring:testing-skills-with-subagents
by LerianStudio
Skill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR).
ring:dev-unit-testing
by LerianStudio
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
ring:dev-fuzz-testing
by LerianStudio
Gate 4 of development cycle - ensures fuzz tests exist with proper seed corpus to discover edge cases, crashes, and unexpected input handling.
ring:dev-cycle-frontend
by LerianStudio
Frontend development cycle orchestrator with 9 gates. Loads tasks from PM team output or backend handoff and executes through implementation → devops → accessibility → unit testing → visual testing → E2E testing → performance testing → review → validation.
ring:dev-cycle
by LerianStudio
Main orchestrator for the 10-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation → devops → SRE → unit testing → fuzz testing → property testing → integration testing (write) → chaos testing (write) → review → validation gates (Gates 0-9), with state persistence and metrics collection. Gates 6-7 (integration/chaos) write and update test code per unit but only execute tests at end of cycle (deferred execution).
testing
by andrelandgraf
Complete testing setup with Neon database branching, Playwright browser tests, integration tests, and unit tests. Isolated branches with automatic TTL cleanup.
takopi-release
by banteg
Prepare and ship a Takopi release. Use when asked to cut a release, bump release versions, update changelog/spec/readme, tag v<major.minor.patch>, or trigger the GitHub release workflow.
bio-binning-qc
by fmschulz
Perform metagenomic binning, refinement, and QC with completeness/contamination checks.
bio-reads-qc-mapping
by fmschulz
Ingest, QC, and map reads with reproducible outputs. Use for raw read processing and coverage stats.
foundups-result-interpreter
by FOUNDUPS
Summarize raw test output, logs, or diffs into a compact worker-friendly report for FoundUps handoff. Use after execution upstream returns artifacts.
workthrough
by bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
prompt-enhancer
by bear2u
Enhance user prompts by analyzing project context (code structure, dependencies, conventions, existing patterns). Use when users provide brief development requests that would benefit from project-specific context to generate more accurate, contextually-aware prompts.
cpp-unit-testing
by sentenz
Automates unit test creation for C++ projects using GoogleTest (GTest) framework with consistent software testing patterns including In-Got-Want, Table-Driven Testing, and AAA patterns. Use when creating, modifying, or reviewing unit tests, or when the user mentions unit tests, test coverage, or GTest.
cpp-mock-testing
by sentenz
Automates mock test creation for C++ projects using Google Mock (GMock) framework with consistent software testing patterns. Use when creating tests with mocked dependencies, interface mocking, behavior verification, or when the user mentions mocks, stubs, fakes, or GMock.
cpp-fuzz-testing
by sentenz
Automates fuzz test creation for C++ projects using Google FuzzTest with consistent software testing patterns. Use when creating fuzz tests, mutation testing, or when the user mentions fuzzing, AFL, or coverage-guided testing.
workthrough
by bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
testing
by the-vibey-project
This skill should be used when adding behavior, repairing a failed gate, changing workflows, or validating a release.
finding-mobility-opportunities
by jupiterx0910
Evidence-driven opportunity discovery for startup ideas, emerging industries, career-to-founder transitions and small-team ownership paths. Finds what a specific operator can enter, validate and turn into owned capital.
claudeloop-testing
by the-vibey-project
Explains claudeloop's testing philosophy and pytest layout — fakes over mocks for every port, FakeClock/FakeSleeper for simulating multi-day waits without real sleeping, mandatory Hypothesis property tests for numeric/time-based invariants, per-layer coverage gates (100% for domain and application), and the documented # pragma no cover policy. Use this whenever writing or modifying any test under tests/, whenever the user asks how to test something in this codebase, mentions coverage, Hypothesis, property-based testing, or asks why a coverage gate failed. Make sure to consult this before adding a mock (this codebase uses fakes implementing real Protocols instead), before adding a numeric or time-based config field without a property test, and before adding a # pragma no cover without a stated reason — all three are enforced review expectations here, not suggestions.