protocol-change

Coordinate worker protocol changes across docs, schemas, and codebases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/StiensGate928/Srtforge --skill protocol-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol-change
Source: https://github.com/StiensGate928/Srtforge/tree/main/.agents/skills/protocol-change
Command: npx skills add https://github.com/StiensGate928/Srtforge --skill protocol-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protocol drift across multiple artifacts when changing worker requests/events is a source of subtle bugs and misalignments. This Skill ensures that updates are applied in lockstep across docs, schemas, and codebases (Python, Rust, TypeScript) along with tests to keep the ecosystem consistent.

Core Features & Use Cases

  • Lockstep protocol updates: Synchronize changes across documentation, JSON schemas, and code implementations.
  • Cross-language consistency: Align Python, Rust, TypeScript components and tests with the new contract.
  • Validation and verification: Run checks and tests to ensure deduced changes pass before handoff.

Quick Start

Run the protocol-change skill to apply and verify lockstep updates across docs, schemas, and code.

Frequently Asked Questions about protocol-change

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

FAQPage Schema
How do I prevent protocol drift when changing worker requests across Python, Rust, and TypeScript?

To prevent protocol drift during a protocol change, you must apply updates in lockstep across documentation, JSON schemas, and codebases in Python, Rust, and TypeScript. This ensures all components and tests remain consistent with the new contract.

What is the best way to synchronize JSON schemas and documentation when reshaping worker event fields?

The best way to synchronize JSON schemas and documentation during a protocol change is to validate doc contracts alongside code implementations. This verifies that Python builders, TypeScript reducers, and Rust requests all compile and pass tests together.

How do I update worker protocol fields across multiple languages without breaking existing tests?

To update worker protocol fields without breaking tests, apply the additions, removals, or reorderings across all languages simultaneously. Run validation checks to ensure Python, Rust, and TypeScript implementations compile and tests pass before handoff.

Can I use a single workflow to rename fields in worker requests across docs and code?

Yes, you can use a coordinated protocol change workflow to rename fields across docs and code. It aligns documentation, JSON schemas, and multi-language codebases including Python, Rust, and TypeScript in a single lockstep update.

When do I need to validate doc contracts and JSON schemas for worker protocol updates?

You need to validate doc contracts and JSON schemas whenever you add, remove, rename, reshape, or reorder fields in worker requests and events. This cross-language verification prevents misalignments between the documentation and the actual code implementations.