replay-transcript-for-regression
/replay-transcript-for-regression
Re-run a stored session against a new build to catch protocol drift before a client does. Use when the server is about to be released and its wire behaviour must not change
- Author
- Wsh7Ash ↗
- Repository
- skillmcp ↗
- Licence
- MIT
- Last repository change
- 29.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Re-run a stored session against a new build to catch protocol drift before a client does. Use when the server is about to be released and its wire behaviour must not change
Original author description
Re-run a stored session against a new build to catch protocol drift before a client does. Use when the server is about to be released and its wire behaviour must not change
How it works
- Procedure
- Signals
- Patterns
- Pitfalls
- Done when
- References
SKILL.md preview
--- name: replay-transcript-for-regression description: "Re-run a stored session against a new build to catch protocol drift before a client does. Use when the server is about to be released and its wire behaviour must not change" pack: skillmcp version: 1.0.0 category: ai-tool tags: [verify, regression, release] --- # Replay Transcript For Regression > Re-run a stored session against a new build to catch protocol drift before a client does **Use when:** the server is about to be released and its wire behaviour must not change **Avoid when:** the release intentionally changes the protocol and new fixtures were written ## Procedure 1. Pick the transcript that covers the most client-visible behaviour 2. Run it against the previous build and store the output as the baseline 3. Run it against the new build with identical input 4. Compare semantically, ignoring declared volatile fields 5. Investigate every difference before deciding it is intended 6. Publish the new baseline only with the release notes that explain it ## Signals - the replay completes without a timeout or crash - differences are limited to fields the release intended to change - the baseline file is committed with the release - a deliberate change appears in the changelog ## Patterns **1. Baseline pair** ```text transcript-before.jsonl and transcript-after.jsonl ``` **2. Semantic compare** ```text parse both, drop volatile fields, diff ``` **3. Explained diff** ```text new field 'instructions' added in 1.1.0 ``` ## Pitfalls - Comparing raw bytes and failing on key ordering - Accepting a diff without checking it against the release intent - Replaying without a timeout so a hung build blocks the release ## Done when - a baseline exists for the previous build and is compared semantically - every difference is either explained in the changelog or fixed ## References - [MCP - lifecycle](https://modelcontextprotocol.io/specification/2025-03-26/basic/lifecycle) - [Semantic versioning](https://semver.org/)
Versions
The database has no other skills named replay-transcript-for-regression.
Database snapshot: 13.11.2026 · package version d1d742a50998 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90session-replay
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools. - 100fixture-driven-transcript-tests
Keep a request/response transcript on disk and assert the server still matches it. Use when a protocol server has behaviours that must not drift across refactors - 100replay
Re-run a past episode offline against the committed regression case set — real human findings on closed PRs — to see how a proposed change to the reviewer would have behaved. Use when asked whether a tweak would still catch what humans caught, to calibrate against the pre-bot… - 100protocol-conformance-test
Test the wire protocol directly, so a client bug and a server bug are distinguishable. Use when a client reports a failure and the server's own behaviour is unproven - 98replay-qa-api
当需要直接从 Codex 调用 Replay QA 的 REST API 时使用。涵盖 bearer token 设置、Replay 录制前置条件、从 Replay 录制或目标 URL 创建项目、轮询、bug 检索、journey、测试运行、探索以及修复工作流规范。 - 100replayio
当需要在 Replay 中录制或检查智能体浏览器运行、使用 Replay Chromium 通过宿主智能体浏览器测试本地应用,或使用 Replay MCP 服务器对已上传的录制进行更深入调试时使用。