Testing & Quality skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

impl-peer-review

Cross-LLM peer review of an implemented change (the diff) via `compozy exec`: an independent reviewer runtime pressure-tests the diff and writes one scoped Markdown findings artifact for user-directed remediation. Project-agnostic — any repo or language; auto-discovers project rule files and the verify command. Use after an implementation pass (feature, bug fix, refactor) when the user explicitly asks for an external review of the diff before commit or PR. Do not use for spec/TechSpec review — use spec-peer-review.

2.37k repo starsObserved in 3 repos

Testing & Quality

spec-peer-review

Cross-LLM peer review of a spec — TechSpec, design doc, RFC, or detailed PRD — run via `compozy exec`, producing one scoped Markdown findings artifact for user-directed incorporation. Use when the user has approved a spec draft and explicitly wants an external review round, especially for autonomy/network/security/migration-impacting designs. Project-agnostic: any repo, any language. Don't use for implementation/diff review (use impl-peer-review) or as an automatic/looping approval gate.

2.37k repo starsObserved in 3 repos

Testing & Quality

cy-final-verify

Enforces fresh verification evidence before any completion, fix, or passing claim, and before commits or PR creation. Use when an agent is about to report success, hand off work, or commit code. Do not use for early planning, brainstorming, or tasks that have not yet reached a concrete verification step.

2.37k repo starsObserved in 1 repos

Testing & Quality

cy-spec-peer-review

Runs an optional cross-LLM peer review of a TechSpec via compozy exec --ide claude --model opus --reasoning-effort xhigh and requires the reviewer to write a scoped Markdown findings artifact for user-directed incorporation. Use when a TechSpec draft has already been approved by the user and they want an external review round, especially for complex or high-risk technical designs. Do not use for PRDs, automatic approval gates, code review batches, or auto-looped review cycles.

2.37k repo starsObserved in 1 repos

Testing & Quality

qa-execution

Runs real-user dogfooding sessions through the product's public interfaces: a persona walks a journey in the browser, takes a thematic tour, probes edges, hunts paper cuts, and reports what a real user would experience. Reads its plan from the living QA docs tree (<qa-docs-path>, default docs/qa/). Use when validating a release candidate, branch diff, migration, or user-facing change against production-like behavior. For planning that tree — personas, journeys, charters, the bug registry — use qa-report; for CI gate runs, AI implementation audits, or integration/security/performance suites, use agent-output-audit.

2.37k repo starsObserved in 1 repos

Testing & Quality

qa-report

Plans real-user QA as living repo docs — the durable <qa-docs-path> tree (default docs/qa/) that every QA cycle appends to. Use when bootstrapping or updating a project's QA docs, planning a cycle before execution (map journeys as flows, derive scenarios, plan persona-driven session charters), or registering bugs into the durable BUG-NNNN registry. Do not use for live session execution, browser evidence, or fix loops — use qa-execution for those.

2.37k repo starsObserved in 1 repos

Testing & Quality

test-mode

Guide for using MPK test mode to unit-test individual layers or multi-layer pipelines through the full compilation pipeline. Use when writing layer tests, debugging kernel output, or validating a new task end-to-end.

2.37k repo starsObserved in 1 repos

Testing & Quality

test-attack-technique

Tests and validates Stratus Red Team attack techniques by executing warmup, detonation, and cleanup phases with comprehensive validation. Validates cloud credentials, parses command output, checks expected outcomes, and generates HTML reports. Use when testing attack techniques, validating TTPs, verifying technique behavior, or when user mentions stratus, warmup, detonate, or technique IDs like aws.*, azure.*, gcp.*, k8s.*, or entra-id.*. Supports AWS, Azure, GCP, Kubernetes, and Entra ID.

2.36k repo starsObserved in 2 repos

Testing & Quality

assertions

Write correct synchronous Gomega assertions — Expect/Ω notation, the To/NotTo/ToNot/Should/ShouldNot equivalences, the multi-return error idiom, Succeed vs HaveOccurred, the .Error() chaining form, annotating assertions (format-string and func()string), tuning failure output via the format subpackage (MaxLength/MaxDepth/UseStringerRepresentation/GomegaStringer/TruncatedDiff/RegisterCustomFormatter/format.Object), and asserting inside helper functions with GinkgoHelper/WithOffset/ExpectWithOffset, NewWithT(t) for plain testing, and the g Gomega callback. Use when writing or reviewing synchronous (non-polling) Gomega assertions.

2.35k repo starsObserved in 1 repos

Testing & Quality

async

Polling assertions in Gomega — Eventually (poll until it passes) and Consistently (must keep passing), the func(g Gomega) callback idiom, WithTimeout/WithPolling/Within/ProbeEvery, WithContext and Ginkgo SpecContext, StopTrying/TryAgainAfter bail-outs, MustPassRepeatedly, and default-interval tuning. Use when an assertion can't be true synchronously — anything involving goroutines, channels, network calls, eventual consistency, or "wait until / stays true".

2.35k repo starsObserved in 1 repos

Testing & Quality