All authors
Claude Skills by mikeparcewski
github.com/mikeparcewski152 skills0 installs61 views
- Qe Ai Feature Test EngineerTier-2 specialist — testing LLM-backed features. Prompt-injection probes (direct / indirect / payload-smuggling / multi-turn), jailbreak library (DAN, grandma, token-smuggling, base64), refusal-rate regression, hallucination drift against a caller-provided golden set, output-drift monitors (JSON-schema, token length, citation fidelity). Use when: LLM feature under test, prompt-injection review, jailbreak sweep, refusal-rate check, hallucination regression, RAG citation audit, "does this AI f...Votes: 0GitHub stars: 9
- Qe Chaos Test EngineerChaos + resilience specialist — failure injection via Toxiproxy, tc, Chaos Mesh, or AWS FIS. Pre-registers a steady-state hypothesis, caps blast radius, writes a rollback plan, and records the experiment as a task + verdict in DomainStore. REFUSES to run against production targets unless the scenario's frontmatter carries `trust_level: production-authorized` AND a `change-ticket:` reference. Use when: resilience testing, chaos engineering, failure injection, game-day design, graceful-degrada...Votes: 0GitHub stars: 9
- Qe Code AnalyzerStatic code analysis for testability, quality, and maintainability. Reviews code structure, identifies test-coverage gaps, and flags risky areas. Use when: static analysis, code-quality metrics, testability assessment, maintainability review, coverage-gap identification. Runs on arbitrary source code, anytime — does not require a spec or an active build phase. NOT THIS WHEN: - Reviewing acceptance criteria for SMART+T (pre-code, no implementation yet) — use `wicked-garden-qe-requirements-qu...Votes: 0GitHub stars: 9
- Qe Compliance Test EngineerRegulatory-control specialist — SOC 2 / HIPAA / GDPR / PCI-DSS evidence collection. Reads a `controls:` list from the scenario frontmatter, executes a deterministic evidence-gathering command per control, and emits an auditor-ready `control-evidence.md` + a control-coverage CSV matrix. Verdict tags each control as satisfied / unsatisfied / out-of-scope. Use when: SOC2 readiness run, HIPAA control mapping, GDPR Article-30 record-of-processing, PCI-DSS scope audit, "prove we have evidence for ...Votes: 0GitHub stars: 9
- Qe Contract Testing EngineerAPI contract testing specialist. Designs and reviews consumer-driven contracts, Pact-style tests, OpenAPI contract verification, schema versioning, and breaking-change detection across service boundaries. Use when: API contract tests, CDC, Pact, OpenAPI verification, schema versioning, breaking-change detection, provider/consumer negotiation.Votes: 0GitHub stars: 9
- Qe Coverage ArchaeologistFind dark corners in legacy code — untested, unreferenced, or low-confidence paths. Prioritizes by risk using coverage + git history + call-graph. Use when: legacy code audit, coverage gap analysis, dark-code discovery, risk prioritization, test-debt assessment.Votes: 0GitHub stars: 9
- Qe Data Quality TesterData-quality specialist — schema drift, referential integrity, migration forward/rollback verification, great_expectations / dbt-test patterns. Use when: data quality checks, schema drift, migration testing, referential integrity, ETL validation, data contract enforcement.Votes: 0GitHub stars: 9
- Qe E2e OrchestratorMulti-service, multi-UI journey orchestration across environments. Coordinates a scenario that spans frontend + API + worker, manages environment, asserts end state. Use when: full-journey E2E, cross-service flows, multi-tab / multi-user coordination, Playwright / Cypress orchestration at scale.Votes: 0GitHub stars: 9
- Qe Exploratory TesterSession-based, unscripted exploratory testing — the agent acts like a human tester. Charter-driven session, note-taking, bug hunting across UI and API. Use when: exploratory testing, unscripted session, charter-based bug hunting, heuristic-driven testing, fresh-eyes pass.Votes: 0GitHub stars: 9
- Qe Flaky Test HunterFlake detection + root-cause specialist. Queries DomainStore for historical verdicts per scenario_id, computes flake rate over a rolling 14d window, reproduces locally with repeat runs, and classifies the cause under a fixed taxonomy (timing / order-dep / env / resource / external-dep). Never proposes "add retry" as a fix. Quarantine is a last resort with a deadline. Use when: flaky tests, retry noise, quarantine review, intermittent failures, test-order dependencies, "this test passes local...Votes: 0GitHub stars: 9
- Qe Fuzz Property EngineerProperty-based and fuzz testing — Hypothesis (Python), fast-check (TS), AFL/libFuzzer for native code. Finds inputs example tests never consider. Use when: property testing, fuzzing, adversarial input, parser / state machine verification.Votes: 0GitHub stars: 9
- Qe Iac Test EngineerInfrastructure-as-Code specialist — terraform validate/plan, checkov, tflint, tfsec, Rego/OPA (opa eval / conftest), Kyverno (kyverno-cli test), CloudFormation Guard (cfn-guard validate), Helm + kubeconform. Captures plan output as evidence, treats "plan-not-clean" as a verdict signal, and records policy conformance per-rule so reviewers can trace which control rejected which resource. Use when: terraform plan drift, k8s policy conformance, helm chart lint, "does this PR violate the SOC2/CIS...Votes: 0GitHub stars: 9
- Qe Incident To Scenario SynthesizerTurns a production incident into a deterministic scenario file that reproduces it. Takes an incident-report markdown OR direct fields (stack trace, endpoint URL, HTTP method, request body), extracts the minimal reproducer, writes `scenarios/<incident-id>.md` with `linked_to_incident:` frontmatter, emits `wicked.qe.scenario.authored` with `source: incident`, and queues a review task under `assignee_skill: incident-to-scenario-synthesizer:review` so a human confirms before the scenario is marke...Votes: 0GitHub stars: 9
- Qe Integration Test EngineerReal-service integration testing — distinct from contract testing. Spins up dependencies (DB, queue, cache) and asserts cross-component wiring. No mocks. Use when: multi-service wiring, database + app tests, queue + consumer tests, ephemeral environments, testcontainers, docker compose for tests.Votes: 0GitHub stars: 9
- Qe Load Performance EngineerLoad + performance testing — k6, locust, hey. SLO validation, P95/P99 assertions, memory/CPU profile review. Use when: load tests, perf regression, SLO validation, capacity planning, throughput ceiling, response-time distribution.Votes: 0GitHub stars: 9
- Qe Localization Test Engineeri18n / localization testing — pluralization, RTL, date/currency formatting, missing strings, pseudolocalization. Use when: i18n audit, RTL layout, pluralization rules, locale-specific formatting, translation coverage, pseudolocalization.Votes: 0GitHub stars: 9
- Qe Mutation Test EngineerMutation-testing specialist — Stryker (JS/TS), Mutmut (Python), Pitest (Java), go-mutesting (Go). Runs a scoped mutation pass, parses the kill report, and writes a kill-rate summary + top surviving mutants with triage priority to the evidence dir. Records a verdict row that distinguishes "weak tests" (coverage present, assertions absent) from "missing tests" (no coverage). Explicitly warns that 100% kill rate may indicate redundant tests. Use when: mutation testing, test-effectiveness audit,...Votes: 0GitHub stars: 9
- Qe Observability Test EngineerAssert that logs, metrics, and traces emit correctly. Verify structured log fields, OpenTelemetry span presence, metric cardinality. Use when: observability testing, log assertions, metric assertions, trace verification, OTel span coverage, cardinality audit.Votes: 0GitHub stars: 9
- Qe Production Quality EngineerMonitor production quality post-deploy. Track SLO targets, error budgets, performance regressions, and canary analysis. Define rollback criteria. Use when: post-deploy, production quality, SLO, error rate, canary, rollback criteria, performance regression.Votes: 0GitHub stars: 9
- Qe Release Readiness EngineerTier-2 specialist — aggregates ledger verdicts, open flakes, risk register, coverage delta, and prod SLO state into a single release-gate verdict: GO / CONDITIONAL / NO-GO with the specific blockers named. The "should we ship" question gets a crisp answer instead of five dashboards. Not a pipeline step — an aggregator. Use when: release readiness, ship decision, release gate, GO/NO-GO, "is this safe to ship", release sign-off, crew phase "cutover", PR ready-to-merge assessment when rigor ma...Votes: 0GitHub stars: 9
- Qe Requirements Quality AnalystEvaluate acceptance-criteria quality at the clarify phase. Check whether ACs are specific, measurable, testable. Flag ambiguous scope and missing edge cases. Use when: clarify-phase AC review, requirements-quality gate, SMART checks. Runs at the clarify gate — after ACs are drafted, before design begins. Pre-code only; no implementation is expected to exist yet. NOT THIS WHEN: - Post-implementation: checking whether code actually satisfies the ACs (spec-vs-code divergence) — use `wicked-gar...Votes: 0GitHub stars: 9
- Qe Risk AssessorIdentify failure modes, assess security/reliability/operational risks, and produce a risk matrix with mitigations. Use when: risk identification, failure-mode analysis, technical-risk review, mitigation planning before build.Votes: 0GitHub stars: 9
- Qe Scenario ExecutorRuns qe scenario files end-to-end. Reads scenario markdown, executes steps via Bash, and writes evidence JSON to .wicked-qe/evidence/{run-id}/. Handles bash commands and CLI tool invocations. Use when: scenario execution, test runner execution, step-by-step execution <example> Context: Running a test scenario to validate behavior. user: "Execute the login-positive scenario to validate the workflow end-to-end." <commentary>Use scenario-executor for full-capability scenario testing including b...Votes: 0GitHub stars: 9
- Qe Security Test EngineerTier-2 specialist — application security testing. SAST orchestration (semgrep, CodeQL), DAST (ZAP, nuclei), secrets scanning (gitleaks, trufflehog, detect-secrets), authz/authn attack patterns (IDOR, role escalation, JWT validation, session fixation, CSRF), OWASP ASVS/WSTG alignment. Use when: security review, SAST scan, DAST scan, OWASP check, JWT/auth testing, secrets-in-repo scan, IDOR check, role escalation test, "is this endpoint secure", vulnerability assessment. NOT THIS WHEN: post-d...Votes: 0GitHub stars: 9
- Qe Semantic ReviewerRender an INDEPENDENT semantic verdict on whether code implements what each acceptance criterion MEANS — not whether the AC id is referenced. Use when: spec-to-code alignment must be judged by meaning, review/build hard gates, 'does the code actually do what the AC described'. NOT THIS WHEN: - Evaluating AC quality itself (SMART+T) before any code is written — use `wicked-garden-qe-requirements-quality-analyst` - General code-quality, complexity, or testability review without a spec — use `w...Votes: 0GitHub stars: 9
- Qe Snapshot Hygiene AuditorSnapshot-rot detector. Scans `__snapshots__/`, `*.snap`, `*.golden`, `cassettes/`, and `.syrupy` directories for four classes of rot: stale (>90d old AND still referenced), over-broad (full-DOM / full-JSON where a narrower assertion would do), rubber-stamped (baseline regenerated in the same commit that introduced the behavior change), and dead (file referenced by no active test). Outputs a ranked remediation list and defaults to a CONDITIONAL verdict with a top-N to re-review. Use when: sna...Votes: 0GitHub stars: 9
- Qe Test Automation EngineerGenerate test code and configure test automation infrastructure. Creates unit, integration, and end-to-end tests. Configures test runners, CI pipelines, coverage, and fixtures. Use when: test generation, automated tests, test code, test infrastructure, CI testing, coverage configuration. Generalist — detects framework and writes tests at any layer. NOT THIS WHEN: - Authoring UI / component-level tests (React/Vue/Svelte component rendering, props, events) — use `wicked-garden-qe-ui-component...Votes: 0GitHub stars: 9
- Qe Test Code Quality AuditorAudits the TEST code itself — not the SUT. Detects assertion-free tests, tautological assertions, try/catch swallowing, shared-state bleed, hardcoded sleeps, nondeterministic seeds, duplicated beforeEach sprawl, slow-per-assertion ratios, and dead tests. Writes a ranked finding list and records a CONDITIONAL or FAIL verdict keyed to severity. This is the "who watches the watchmen" agent — complements flaky-test-hunter, which focuses on runtime behavior rather than static smells. Use when: te...Votes: 0GitHub stars: 9
- Qe Test Data ManagerFixtures, factories, anonymized production snapshots. factory_boy / fishery patterns, PII scrubbing, referentially-consistent synthetic data. Use when: test data design, fixtures, factories, anonymized snapshots, seed data, referential consistency.Votes: 0GitHub stars: 9
- Qe Test DesignerDEV-LOOP FAST PATH ONLY. Single-role plan→execute→verdict for local iteration when the 3-agent isolated pipeline's rigor is explicitly not needed. Reads scenarios, produces evidence-gated test plans, executes steps, and renders a verdict — all in one accountable role. Use when: rapid dev-loop iteration on a single engineer's workstation, scaffolding a scenario before wiring it into wicked-garden-qe accept, quick smoke on throwaway branches. DO NOT use when: the verdict needs trustworthy pro...Votes: 0GitHub stars: 9
- Qe Test Impact AnalyzerTier-2 specialist — answers "given this diff, which tests must I run?" Consumes git diff, the estate capability graph (changed-since/BlastRadius over endpoint + affordance nodes), call-graph signal, and historical coverage from the DomainStore ledger to rank existing scenarios by probability of catching a regression in the change. The answer to the #1 question every CI conversation has: "why did we run all these tests for a one-line change?" Use when: test impact analysis, TIA, selective tes...Votes: 0GitHub stars: 9
- Qe Test OracleAnswers plain-language questions about the qe data domain. Queries SQLite via the fixed parameterized oracle query library. Returns structured markdown or JSON answers. Read-only contract. Use when: "what scenarios exist", "last verdict", "show failed runs", "what tasks are open", "show test history", "query test data" <example> Context: User wants to know the test history for a project. user: "What was the last verdict for the self-test scenario?" <commentary>Use test-oracle to query the SQ...Votes: 0GitHub stars: 9
- Qe Test StrategistGenerate test strategies and coverage plans from code and requirements. Identifies happy paths, error cases, and edge cases with positive+negative pairing. Writes strategy records to the DomainStore. Use when: test planning, coverage strategy, what to test, test scenarios, risk assessment <example> Context: New feature needs a test strategy before implementation. user: "What test scenarios do we need for the file upload feature?" <commentary>Use test-strategist to identify comprehensive test...Votes: 0GitHub stars: 9
- Qe Testability ReviewerReview design artifacts and code structure for testability. Flags designs that will be hard to test. Checks component isolation, dependency injection readiness, and boundary clarity. Use when: design-phase testability review, component isolation checks, dependency injection assessment, mockability, seams.Votes: 0GitHub stars: 9
- Qe Ui Component Test EngineerComponent-level UI testing — React Testing Library, Vitest, Testing Library for Vue/Svelte. Render a single component with props, interact, assert. Distinct from E2E and visual regression. Use when: component tests, RTL, Vitest, Jest DOM, props-in / rendered-out tests, hooks testing.Votes: 0GitHub stars: 9
- Qe Visual Regression EngineerSnapshot + perceptual-diff specialist. Playwright for capture, pixelmatch / odiff for diff, dynamic-region masking via CSS selectors, cross-browser matrix (chromium / firefox / webkit). Tracks baseline provenance (who approved, when) and refuses to auto-update baselines. Writes diffs to the evidence dir and records a verdict that distinguishes threshold exceeded from "new baseline pending approval". Use when: visual regression tests, pixelmatch / odiff, baseline updates, storybook snapshot t...Votes: 0GitHub stars: 9
- QeConsolidated quality-engineering domain: evidence-gated testing from strategy to verdict. Nine actions — setup, plan (strategy, risk, testability, AC quality), author (scenarios, test code, fixtures), campaign (three-lens repo recon → a dependency-ordered scenario ladder), intake (plan as a crew HITL gate), execute (run scenarios, capture evidence), review (independent verdicts, suite quality), insight (ledger stats, flake detection, coverage archaeology), accept (the isolated 3-agent pipelin...Votes: 0GitHub stars: 9
- Repo LearnLearn an unfamiliar repo the way a senior engineer does: follow where the code actually churns, find what that churn touches that the rest of the system leans on, read the load-bearing code for real, then write down BOTH what you learned (knowledge) and what should hold (policies) — as inert estate proposals a human reviews, never as asserted fact. Three BOUNDED phases, one wicked-crew unit each: (1) CHURN — sampled git churn → ranked active areas (top-N cap); (2) HOTSPOTS — hotspots + blast...Votes: 0GitHub stars: 9
- SearchCode-intelligence search over wicked-estate's static + injected code-relationship graph (ADR 0005): index (build/refresh), blast-radius (dependents), lineage (data/dependency flow), path (the ordered hops from A to B), hotspots (PageRank centrality), service-map (infra + code), narrate (orientation walkthrough). Every graph read is ONE call on every seat, in every session kind — the read-only estate shim (`wicked-garden run scripts/_estate_client.py --readonly call …`). Use when: "index the ...Votes: 0GitHub stars: 9
- Codebase NarratorNarrate codebase structure and architecture for orientation — directory layout, key modules, data flows, technical decisions, and code health. A query + synthesis capability rather than a persistent role; produces a guided reading order and flags gotchas for newcomers. Use when: "give me an architecture walkthrough", "narrate this codebase", "explain how this project is organized", "code navigation", "where should I start reading".Votes: 0GitHub stars: 9
- SwarmParallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove, wicked-vault attestation, and the worktrees + deliberate skills rather than reinventing them. This is multi-AGENT parallel execution+verification; for independent multi-MODEL perspe...Votes: 0GitHub stars: 9
- WickedizerWriting humanizer / AI-tell remover (the team's house writing-cleanup skill). Use when writing, rewriting, or humanizing content: strips AI tells (fluff, hedging, promo language, chatbot artifacts) while preserving meaning, and aligns output to a direct, practical, action-oriented team voice. Use when: humanizing AI-sounding prose, "remove AI tells", "make this sound human", drafting a PR description or commit message, or aligning written output to team voice. Aliases: humanize, humanizer, d...Votes: 0GitHub stars: 9
- WorkflowReference for how the wicked-crew workflow engine operates — phase catalog, gate enforcement, rigor tiers, and facilitator rubric. Use when understanding or troubleshooting crew phase mechanics (gate config, CONDITIONAL resolution, phase dependencies). NOT for starting a project (use crew:start) or proposing a process plan (use propose-process).Votes: 0GitHub stars: 9
- WorktreesGit worktree hygiene — when to create, how to clean up, and what fails silently. Captures three classes of bug that recur with worktree-based agent isolation: subagent dangling commits, orphan branches with unique work, and time-sensitive dangling-commit garbage collection. Includes detection commands, the salvage decision flow, and the trust-but-verify rule for subagent commit reports. Use when: a subagent reports a commit SHA, after a worktree-based agent finishes, cleaning up `.claude/wor...Votes: 0GitHub stars: 9
- Acme Seo RankerRanking analyst. Part of the broken fixture: it is referenced by the scraper's NOT-THIS-WHEN but deliberately does not point back.Votes: 0GitHub stars: 9
- Acme Seo ScraperScrapes SERPs. Deliberately BROKEN: this is a worker ({vendor}-{domain}-{role}) but it declares no metadata.role: worker. NOT THIS WHEN: ranking analysis — use `acme-seo-ranker` (which deliberately does NOT point back, breaking reciprocity).Votes: 0GitHub stars: 9
- Wicked Garden Seo ThiefDeliberately BROKEN: claims the reserved wicked-garden prefix from a third-party pack. Must trip PK013 (vendor prefix) — the wicked-* namespace belongs to the first-party catalog.Votes: 0GitHub stars: 9
- Acme Seo Content AuditorOn-page SEO auditor — crawls the given pages, checks title/meta/heading structure, internal linking, and content-keyword alignment, then records an evidence-backed seo-audit verdict via wicked-vault (never self-asserted). Use when: "audit this page", "SEO review", "why does this page not rank", "meta description review", "content audit with a verdict". NOT THIS WHEN: greenfield keyword strategy with no page to audit — use `acme-seo-keyword-analyst` (the strategy twin); this skill judges exi...Votes: 0GitHub stars: 9
- Acme Seo Keyword AnalystKeyword research specialist — builds a keyword map with intent clusters (informational / navigational / transactional), estimates difficulty from SERP snapshots, and proposes a target-page mapping. Use when: "keyword research", "what should we rank for", "search intent", "keyword gap vs competitor". NOT THIS WHEN: an existing page needs an on-page audit with a recorded verdict — use `acme-seo-content-auditor` (it writes evidence and its verdict is gate-checkable); this skill produces strate...Votes: 0GitHub stars: 9
- Acme SeoACME SEO domain router: keyword research, content audits, and ranking verdicts with recorded evidence. Two actions — keywords (dispatch the keyword analyst) and audit (dispatch the content auditor; its verdict is recorded via wicked-vault so "done" is re-derived, never asserted). Use when: "keyword research", "SEO audit", "why don't we rank", "content optimization", "meta description review".Votes: 0GitHub stars: 9