failure-replay-engine

Record and recall failure history across commits, deployments, tests, and fixes.

20|3|Updated Apr 30, 2026

Search Tags:#planning #testing #deployment #commit #bug-fix #failure-replay #failure-history

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill failure-replay-engine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: failure-replay-engine
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/failure-replay-engine
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill failure-replay-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FlowDeck remembers every failure recorded in this repo. Before making a change, check the failure history for patterns that match your current task.

Core Features & Use Cases

Failure tracking across reverted commits, failed deployments, flaky tests, and bug fixes.
Guided workflows for before/after editing, including querying history and recording new failures.
JSON-based failure entries with fields such as id, type, description, affected_paths, root_cause, fix_applied, and tags.

Quick Start

Record a failure entry into the history to begin leveraging the replay engine.

Frequently Asked Questions about failure-replay-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track recurring bug fixes and failed deployments across code changes?▼

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.

What is the best way to prevent repeating the same software bugs in my development workflow?▼

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.

How do I record a new failure entry into the failure history?▼

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.

Can I query past flaky tests and reverted commits before making new code changes?▼

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.

Does this failure tracking workflow require any external dependencies or testing frameworks?▼

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.

What limitations exist when analyzing deployment failures and root causes in 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.