replay

Identify and retry discarded experiments after architectural changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SteeZyT33/perf-lab-plugin --skill replay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replay
Source: https://github.com/SteeZyT33/perf-lab-plugin/tree/main/skills/replay
Command: npx skills add https://github.com/SteeZyT33/perf-lab-plugin --skill replay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps re-evaluate experiments that were previously discarded, especially after architectural changes, to identify potential new optimizations.

Core Features & Use Cases

  • Candidate Identification: Automatically finds experiments that were marked as discarded before the last architectural change.
  • Impact Assessment: Explains why a previously failed experiment might succeed now due to specific architectural modifications.
  • Selective Retrying: Retries the most promising discarded experiments to potentially improve performance.

Quick Start

Use the replay skill to find and retry old experiments that might work now.

Frequently Asked Questions about replay

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

FAQPage Schema
How do I retry discarded optimization experiments after architectural code changes?

Re-evaluate discarded optimization experiments by analyzing experiment history against recent changelogs to determine viability, identifying which previously failed hypotheses might now succeed and positively impact performance due to specific architectural modifications.

What is the best way to identify previously failed code changes for re-evaluation?

Identify previously failed code changes for re-evaluation by automatically scanning experiment history to find optimization hypotheses marked as discarded prior to the last architectural change, then assessing their potential impact in the evolving codebase.

How does architectural modification impact the viability of old regression testing hypotheses?

Architectural modification impacts regression testing hypothesis viability by altering the underlying codebase structure, which can resolve previous bottlenecks and allow previously discarded performance tuning experiments to succeed and deliver new optimizations.

Can I selectively retry only the most promising discarded performance tuning experiments?

You can selectively retry the most promising discarded performance tuning experiments by analyzing experiment history and changelogs to filter out hypotheses with the highest potential impact, facilitating targeted re-evaluation without testing every discarded change.

When should I not re-evaluate old optimization hypotheses in an evolving codebase?

You should not re-evaluate old optimization hypotheses when the architectural changes are unrelated to the original failure points, or when the experiment history lacks sufficient context to accurately assess the potential impact of retrying the discarded code changes.