Use 901 to run one feature end-to-end through SpecFlow's full pipeline as a single git-tracked run: high-level design, happy-path specs, scenario-by-scenario test-driven build-out validated and committed per module, cleanup, an optional expanded-coverage round, and a merge back to the base branch. Every design/spec…
A testing workflow for y3 games, with three mandatory rules: review code before sending it, treat only [run-ok] as success, and ensure every run or Lua command reaches the command-ID success marker.
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
Use when building, running, or testing an iOS app on a simulator — claims a leased simulator through simlease so parallel AI agents never collide, labels the simulator window with the task name, and releases it when done.
Hunt for bugs in distributed consensus protocol implementations using a 2-agent strategy+testgen pipeline. Use when targeting consensus protocols (Raft, PBFT, HotStuff, Tendermint, etc.) for automated vulnerability discovery.
SAP UI5 test automation via Playwright CLI. Use when testing SAP Fiori apps, discovering UI5 controls, debugging Praman tests, or automating SAP workflows. Extends playwright-cli with SAP/UI5 awareness.
Adversarial verification agent that tests implementations by running builds, tests, and probing edge cases. Returns a structured VERDICT (PASS/FAIL/PARTIAL) with evidence.
Use when developing or testing Palm OS applications in the POSE64 emulator, including using MCP tools, automating emulator actions, or writing Palm app test scripts.
A batch verification process that checks proof-of-concept items against a list of assets. It runs the checks in parallel and produces a results matrix and Markdown report.
Samurai scoped testing framework for Go (github.com/zerosixty/samurai). MUST use when writing, modifying, reviewing, or debugging Go tests that import samurai, or reference samurai.Run, samurai.RunWith, samurai.Scope, samurai.TestScope, samurai.W, or samurai.BaseContext.
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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 for test-first development.
This sop guides the implementation of code tasks using test-driven development principles, following a structured Explore, Plan, Code, Commit workflow. It balances automation with user collaboration while adhering to existing package patterns and prioritizing readability and extensibility. The agent acts as a…
Plan, generate, execute, analyze, and report k6 performance tests for REST/HTTP and gRPC endpoints, journeys, or whole applications. Use for load, stress, spike, soak, scalability, latency, throughput, and service performance, including approved mutations and remote non-production targets. Excludes production…
BF project testing workflow for Claude Code. Use when generating or maintaining UI automation testing assets from requirements documents or UI exploration, including BF project initialization, sprint0 full test generation, sprintN incremental updates, test case Excel generation, Playwright E2E script generation…
A testing and quality-checking toolkit for running an application, finding bugs, and creating automated tests. It supports API tests and browser-based UI tests in Python or Java.
Test harness for the Signal Prospecting Kit v4.1. Runs deterministic checks and rubric-based grading against all 6 skills including tool connections, multi-batch flow, LinkedIn outreach, channel selection, self-improvement loop, enrichment tiers, bridge/CTA variation, variation planning, and fallback tool detection.…
Prepare dynobox packages for release to npm. Use this skill whenever the user asks to release, publish, ship, bump, or cut a version of any dynobox package — including dry runs, version bumps, changelog updates, and git tagging. Also trigger when the user asks about the release process or wants to verify publish…
Run and audit CC Port's opt-in live Windows package E2E and broader native remaining-scope validation. Use when validating that a packaged installer or release candidate can enable AI automation, upload/download a harmless Skill through packaged MCP plus desktop approval, verify Registry v1 and Git blob bytes, or when…
★not rated 10 18d agoA136 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: