Enforce structured root cause analysis before code changes in development workflows.
npx skills add https://github.com/escoffier-labs/brigade --skill refire
Please help me install this Agent Skill. Skill: refire Source: https://github.com/escoffier-labs/brigade/tree/main/registry/skills/refire Command: npx skills add https://github.com/escoffier-labs/brigade --skill refire
When software breaks—failing tests, production bugs, build breaks, or flaky behavior—teams often rush to quick fixes that mask the underlying issue, leading to repeat incidents, longer downtime, and compounded technical debt, especially under pressure like CI blocking deployments.
Use the refire skill to investigate the root cause of the failing end-to-end test suite in the current repository before proposing any code changes.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a failing CI pipeline, reproduce the issue, audit recent changes, validate documented contracts, and pin a failing test before making any code changes. This structured root cause analysis prevents quick fixes that mask underlying software failures.
Debugging flaky tests requires a structured root cause investigation: reading full error details, reproducing the issue, auditing recent changes, and comparing against working examples. Fix guardrails enforce writing a hypothesis and pinning a failing test before applying minimal single-variable changes.
Production incidents recur because emergency patches often mask underlying issues without tracing the root cause. Applying structured root cause analysis with hypothesis testing and contract validation eliminates repeat failures caused by unrooted quick fixes during incident response.
Yes, structured debugging works under deployment pressure by enforcing guardrails against guesswork. It requires a written hypothesis, a pinned failing test asserting the broken contract, and automatic escalation after three failed fix attempts to prevent compounding technical debt.
Stop trying random fixes for build breaks after three failed fix attempts, which triggers automatic escalation. A formal root cause analysis is needed to compare against working examples and check documented contracts instead of tweaking configs to force a green build.
derHakenTrace data flow and apply a four-phase process to fix root causes.
darkmatterTrace root causes of bugs and test failures before proposing fixes.
nksethDefine SLOs, SLIs, and error budgets to quantify service reliability.
Remedy92Generate hypotheses and collect logs to debug JavaScript, Python, and Node backends.
