haru3613
- 8 skills
- 0 followers
- 8 hours ago last updated
- ▌ Advise · haru3613 bundleDiagnose 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".
- ▌ Diagnose · haru3613 bundleRoot-cause an already-triaged product defect by building a red-capable, deterministic reproduction when safe, then ranking falsifiable hypotheses and emitting a Diagnosis Receipt. Use for a product defect needing substantial root-cause investigation. This skill diagnoses; it does not edit product code. Triggers: "/diagnose", "root-cause this product defect", "diagnose BUG-ID".
- ▌ Hs Setup · haru3613Configure 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`.
- ▌ Test Plan · haru3613 bundlePlan risk-based verification for a task or release, or create an optional reusable Test Contract when the user wants one. Use when asked to plan tests or define release criteria.
- ▌ Bug Workflow · haru3613 bundleTriage a finding that needs tracking, investigation, or handoff. Preserve expected/actual behaviour, evidence, and repair/retest conditions in the existing issue or chosen record.
- ▌ Release Gate · haru3613Assess whether a candidate is ready to release from current scope, actual test evidence, and remaining risks. Return GO, GO WITH CAVEATS, or NO-GO without performing the release.
- ▌ Testing Workflow · haru3613 bundleTest a candidate using current task scope, existing coverage, and concrete risks. Report what passed, what failed, and what remains unverified. Use when asked to test a release candidate or verify an artifact.
- ▌ Exploratory Testing · haru3613 bundleExplore 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".