revamp-cookbook

Update legacy Valkey-Samples cookbooks to current contribution and CI standards.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/edlng/agents --skill revamp-cookbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revamp-cookbook
Source: https://github.com/edlng/agents/tree/main/skills/universal/revamp-cookbook
Command: npx skills add https://github.com/edlng/agents --skill revamp-cookbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the inconsistency and technical debt in archived Valkey-Samples cookbooks by providing a structured, contract-driven workflow to update them to current contribution standards.

Core Features & Use Cases

  • Archive Fidelity: Ensures archived content is preserved while applying necessary updates to meet current CONTRIBUTING.md requirements.
  • Validation & CI: Coordinates language-specific CI workflows and performs exhaustive execution of all Markdown code blocks to ensure technical accuracy.
  • Use Case: Use this when you need to refresh an outdated cookbook from the archive/main-pre-reorg branch, ensuring it aligns with modern Valkey project APIs and passes all automated validation checks.

Quick Start

Use the revamp-cookbook skill to identify an outdated cookbook and begin the local drafting process according to current repository guidelines.

Frequently Asked Questions about revamp-cookbook

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

FAQPage Schema
How do I update legacy Valkey-Samples cookbooks to meet current contribution guidelines?

Updating legacy Valkey-Samples cookbooks requires comparing archived baselines against modern project requirements and CI infrastructure. This structured workflow ensures all code examples are runnable, idempotent, and compliant with the latest API and security policies.

What is the best way to validate Markdown code blocks in Valkey documentation for CI?

Validating Markdown code blocks in Valkey documentation involves coordinating language-specific CI workflows and performing exhaustive execution of all code blocks. This ensures technical accuracy and compliance with current validation standards.

How does cookbook refactoring handle archived content fidelity in Valkey projects?

Cookbook refactoring ensures archive fidelity by preserving archived content while applying necessary updates to meet current CONTRIBUTING.md requirements. This maintains historical context while achieving modern technical validation standards.

Do I need specific CI infrastructure to refresh outdated Valkey cookbooks?

Yes, refreshing outdated Valkey cookbooks requires coordination with language-specific CI workflows to ensure all code examples pass automated validation checks. This infrastructure is necessary to verify compliance with modern Valkey project APIs.

When should I use a structured workflow to regenerate Valkey cookbooks?

You should use a structured workflow to regenerate Valkey cookbooks when refreshing outdated content from the archive or main-pre-reorg branch. This ensures alignment with modern APIs and passing all automated validation checks.

What are the limitations of manually updating archived Valkey-Samples documentation?

Manually updating archived Valkey-Samples documentation lacks the contract-driven validation needed to ensure all code examples are runnable, idempotent, and compliant. Without structured CI coordination, technical accuracy and security policy adherence may be compromised.