failure-replay-engine

To track recurring bug fixes and failed deployments across code changes, this failure-replay engine analyzes commit history, test results, and deployment failures to surface recurrence patterns and stores structured failure entries in a JSON file.

The best way to prevent repeating software bugs is to query a structured failure history before editing code, checking past reverted commits, flaky tests, and root causes against your current task to guide planning and prevent duplicate incidents.

To record a new failure entry into the failure history, apply the guided workflow to log the incident with fields for type, description, affected paths, root cause, fix applied, and tags into the local JSON-based tracking file.

Yes, you can query past flaky tests and reverted commits before making new code changes by using the provided workflow to search the stored failure history, matching patterns from previous incidents to your current development context.

No, this failure tracking workflow does not require external dependencies or specific testing frameworks, operating entirely within the FlowDeck context to analyze existing commits, deployments, tests, and fixes using a local JSON file.

A limitation of analyzing deployment failures in a local JSON file is that failure history is restricted to repository-specific entries, meaning cross-repository recurrence patterns or distributed deployment contexts are not captured in the local tracking structure.