← all publishers

BlizzardBlast

@blizzardblast source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Debug · blizzardblast bundle

   Use when the user asks to investigate, diagnose, troubleshoot, reproduce, or determine the root cause of a concrete failure, regression, flaky behavior, failing test, production incident, or environment-specific defect before editing. Produces a read-only evidence-backed investigation with reproduction status, causal trace, hypothesis ledger, and CONFIRMED/LIKELY/UNRESOLVED/NOT_A_DEFECT status.
   0
   installs
2. ▌
   Code Review · blizzardblast bundle

   Use when the user asks to review code, a PR, diff, current changes, merge readiness, repository risks, targeted files, CI/tooling changes, or stale review comments. Produces a read-only evidence-backed review with coverage, severity-ranked findings, and an APPROVE/COMMENT/REQUEST_CHANGES decision. If fixes are requested, emit the ledger first and hand remediation to iterative-self-review.
   0
   installs
3. ▌
   Test Strategy · blizzardblast bundle

   Use when the user asks to design, review, refine, or assess a risk-based testing strategy for a concrete feature, defect, migration, diff, release, or system boundary. Produces a read-only repository-grounded strategy covering risks, contracts, scenarios, data, environments, execution, residual risk, completeness, and test readiness.
   0
   installs
4. ▌
   Implementation Plan · blizzardblast bundle

   Use when the user asks to create, review, refine, scope, or sequence an implementation plan for a concrete codebase change before editing. Produces a read-only repository-grounded plan with affected boundaries, ordered anchored steps, verification, risks, completeness, and READY_TO_IMPLEMENT/READY_WITH_ASSUMPTIONS/NOT_READY status. Do not use for defining unresolved required behavior, direct implementation, diagnosis, review decisions, execution, or ledger remediation.
   0
   installs
5. ▌
   Change Specification · blizzardblast bundle

   Use when the user asks to define, review, refine, or clarify required behavior, scope, acceptance criteria, edge cases, or contracts for a concrete codebase change before implementation planning. Produces a read-only repository-grounded, implementation-neutral specification with requirements, observable acceptance criteria, affected contracts, assumptions, completeness, and planning readiness. Do not use for root-cause investigation, file-level implementation planning, test strategy, execution, merge review, or ledger remediation.
   0
   installs
6. ▌
   Iterative Self Review · blizzardblast bundle

   Use only when explicitly invoked for an issue ledger, remediation request, repeated fix-and-recheck loop, or post-review repair. Fixes scoped findings in bounded passes against a recorded baseline and reports scoped verification without claiming the whole repository is clean.
   0
   installs
7. ▌
   Implementation Execution · blizzardblast bundle

   Use when the user asks to execute, continue, or resume an existing approved repository-grounded implementation plan. Performs bounded edits one coherent step at a time, verifies each step, preserves invariants and unrelated work, records plan conformance, and stops on material deviation. Do not use for specification or plan creation, ordinary direct implementation, diagnosis, review, or ledger remediation.
   0
   installs