SkillVaultskills Browse all 1,000+ skills

Testing · Version 1.0.0 · Reviewed 2026-08-02

Blocking Bug Correlation Analyst

Design confidence for change-to-bug correlation and release blocker relevance review with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Correlates a change with open blocking defects by component, path, mechanism, and test surface. It grounds the decision in the change diff, blocking bug evidence, affected components, failing tests, ownership, and resolution status and explicitly prevents keyword overlap linking unrelated bugs or missing a shared mechanism expressed with different component names.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Change-to-bug correlation
  • Release blocker relevance review
  • Shared failure mechanism analysis

How Blocking Bug Correlation Analyst works

You provide

Suite structure, failure history, and the behavior to protect

It inspects

Nondeterminism and coverage gaps affecting change-to-bug correlation

It decides

A release blocker relevance review plan at the cheapest useful test level

You verify

The test fails when behavior breaks, not only passes when correct

What it checks first

Blocking Bug Correlation Analyst correlates a change with open blocking defects by component, path, mechanism, and test surface. It grounds the decision in the change diff, blocking bug evidence, affected components, failing tests, ownership, and resolution status and explicitly prevents keyword overlap linking unrelated bugs or missing a shared mechanism expressed with different component names. Use it when the work involves Change-to-bug correlation, Release blocker relevance review, Shared failure mechanism analysis.

  1. Whether the test asserts observable behavior or couples to implementation detail.
  2. Sources of nondeterminism: time, ordering, concurrency, shared state, and network.
  3. Whether a failing test fails for the intended reason, verified by breaking the behavior deliberately.
  4. The balance of the suite, since end-to-end-heavy suites are slow and flaky by construction.

Failure modes it recognizes

  • A fixed sleep standing in for a condition wait, producing failures that track machine load.
  • Tests passing alone and failing in suite because of leaked global or database state.
  • Over-mocking that verifies the mock rather than the integration, so production still breaks.
  • Assertions on unordered collections that pass until the implementation changes iteration order.
  • Coverage measured while assertions are absent, so lines execute without being verified.

Answers it will reject

  • Retrying a flaky test to make CI green, which hides a real intermittent defect.
  • Chasing a coverage percentage, which produces tests that execute code without checking behavior.
  • Writing an end-to-end test for logic a unit test could cover deterministically.

Decision rules it applies

  • Choose the cheapest test level that can actually observe the failure mode.
  • Treat a flaky test as a defect with an owner and a deadline, never as noise.
  • Every bug fix gets a test that fails before the fix and passes after it.

Evidence it asks for

  • Run the suite in randomized order to expose inter-test dependencies.
  • Track flake rate per test over time rather than treating each failure as isolated.
  • Verify a new test fails when the behavior is broken, not only that it passes when correct.

The method inside

  1. Establish what is actually true about change-to-bug correlation from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind release blocker relevance review rather than restating the symptom.
  3. Choose the smallest defensible change for shared failure mechanism analysis, weighing impact, confidence, effort, and reversibility.
  4. Define CI signals and release gates

Deliverables

  • Change-to-bug correlation assessment
  • Release blocker relevance review decision and action plan
  • Shared failure mechanism analysis verification checklist

Evidence requirements

  • System risks and architecture boundaries
  • Existing tests, failures, and coverage evidence
  • Release cadence and supported environments

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the blocking bug correlation analyst to our current change-to-bug correlation work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with the change diff, blocking bug evidence, affected components, failing tests, ownership, and resolution status. The highest-risk failure is keyword overlap linking unrelated bugs or missing a shared mechanism expressed with different component names. Require at least one structural or behavioral link and state confidence when only component proximity is known. Verify the result by having component owners review high-risk correlations and testing the shared path when a reproduction exists.

Boundaries and compatibility

Ideal for

  • Change-to-bug correlation: produce a decision or artifact grounded in supplied evidence.
  • Release blocker relevance review: produce a decision or artifact grounded in supplied evidence.
  • Shared failure mechanism analysis: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Chasing line coverage without risk coverage
  • Replacing integration evidence with mocks

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.