retrospective-validation

Analyze historical validation runs and deployments to compute false pass/fail rates and confidence scores.

2|Updated Apr 8, 2026

Search Tags:#validation #retrospective #post-mortem #evidence #confidence-score #false-pass #revert-rate

Ready to run

npx skills add https://github.com/krzemienski/validationforge --skill retrospective-validation-krzemienski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective-validation
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/retrospective-validation/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill retrospective-validation-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze whether a validation methodology actually worked by examining historical validation runs, deployments, and incident history to surface missed bugs, false alarms, and process weaknesses.

Core Features & Use Cases

Collect Historical Evidence: Aggregate past validation reports, git deploy history, build logs, and incident post-mortems into a single retrospective evidence folder.
Quantitative Analysis: Calculate PASS/FAIL rates, false PASS/FAIL rates, revert frequency, mean time to detect, and evidence quality to measure validation accuracy.
Correlation & Recommendations: Map incidents to validation gaps, identify recurring patterns, compute a confidence score, and produce actionable recommendations for process changes.

Quick Start

Run a retrospective analysis over recent validation reports and deploy history to compute false pass/fail rates, revert frequency, and a confidence score and save the findings to e2e-evidence/retrospective/.

Frequently Asked Questions about retrospective-validation

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

FAQPage Schema

How do I measure the effectiveness of my CI/CD validation process using post-mortem data?▼

Measuring validation effectiveness involves analyzing historical validation runs, git deploy history, CI/CD logs, and incident post-mortems to calculate false pass/fail rates, revert frequency, and a confidence score.

What is a false pass rate in retrospective validation analysis?▼

A false pass rate in retrospective validation analysis quantifies the frequency of deployments that passed validation checks but subsequently triggered incidents or required reverts, revealing gaps in test coverage.

How do I calculate revert frequency and evidence quality from historical deployment outcomes?▼

Calculating revert frequency and evidence quality requires aggregating past validation reports and incident post-mortems to correlate deployment outcomes with validation gaps, ultimately producing a quantitative confidence score.

Can I use this retrospective validation analysis with my existing git deploy history and build logs?▼

Yes, retrospective validation analysis directly ingests existing git deploy history, CI/CD build logs, and validation reports to map incidents to validation gaps and compute quantitative effectiveness metrics.

What's the best way to map incident post-mortems to validation gaps in my software engineering workflow?▼

Mapping incident post-mortems to validation gaps is best achieved by aggregating historical evidence and deployment outcomes to identify recurring patterns, compute a confidence score, and generate actionable process recommendations.

What format does the retrospective validation report use for storing quantitative metrics?▼

The retrospective validation report uses a structured format stored in the e2e-evidence/retrospective/ directory, containing quantitative metrics, correlation analyses, and a computed confidence score.