haru3613

advise

Diagnose a project's test gaps and name the cheapest next tests. Use after hs-setup, after plugin install, or when someone asks what to test, which framework to add, whether coverage is enough, or to audit the test suite. Triggers: "/advise", "what should we test", "which test framework", "is coverage enough", "audit this project's tests", "quality report".

bug-workflow

Turn a test non-pass into one traceable Bug Case, classify it before diagnosis, and route it to the correct owner without losing evidence. Use after testing-workflow records FAIL, FLAKY, BLOCKED, or NOT TESTED, or when someone asks to triage a test finding.

diagnose

Root-cause an already-triaged product defect by building a red-capable, deterministic reproduction when safe, then ranking falsifiable hypotheses and emitting a Diagnosis Receipt. For a test finding, use only after bug-workflow supplies a stable BUG-ID classified product-defect. This skill diagnoses; it does not edit product code. Triggers: "/diagnose", "root-cause this product defect", "diagnose BUG-ID".

exploratory-testing

Explore a completed feature before automating it, then read the existing test system and add the minimum sufficient regression coverage in the same context. Use when a new feature is runnable, when automation is about to be written, or when someone asks for exploratory testing. Triggers: "/exploratory-testing", "explore this feature", "test this manually before automating it".

hs-setup

Configure the small amount of project policy Harness Ship cannot safely infer when a workflow needs it. Empty and early repositories are valid inputs. Triggers: "/hs-setup", "set up harness-ship", "configure harness-ship", "harness-ship setup", or immediately after `/plugin install harness-ship`.

release-gate

Evaluate an exact release candidate against its approved Project Test Baseline and Release Delta, then return GO, GO WITH CAVEATS, or NO-GO without promoting it. Use when someone asks whether a candidate is ready to release. Triggers: "/release-gate", "is this ready to release", "run the release gate", "go or no-go".

test-plan

Create or revise the user-approved Test Contract that defines what must be proven before release. Use when the user wants approved release criteria, a Project Test Baseline, or a release-specific delta. Triggers: "/test-plan", "plan the tests", "define the release criteria".

testing-workflow

Execute an approved Test Contract against an exact non-production candidate, preserve every attempt, and produce the evidence consumed by release-gate. Use after a candidate handoff or when someone asks to test a release candidate. Triggers: "/testing-workflow", "test this candidate", "verify this artifact".