rugo-runmd

Validate Rugo code snippets in Markdown files and verify outputs.

24|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/rubiojr/rugo --skill rugo-runmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rugo-runmd
Source: https://github.com/rubiojr/rugo/tree/main/extras/claude/skills/rugo-runmd
Command: npx skills add https://github.com/rubiojr/rugo --skill rugo-runmd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all Rugo code examples embedded within your Markdown documentation are valid, up-to-date, and produce the expected output, preventing documentation rot.

Core Features & Use Cases

  • Code Block Validation: Parses Markdown files to find and compile all ```ruby code blocks.
  • Output Verification: Optionally runs code snippets and compares their output against a following ```text block.
  • Use Case: After updating Rugo language features, run this Skill on your documentation to automatically confirm that all code examples still compile and function as intended.

Quick Start

Verify all Rugo code examples in the documentation file docs/quickstart.md.

Frequently Asked Questions about rugo-runmd

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

FAQPage Schema
How do I validate Rugo code blocks in markdown documentation?

To validate Rugo code blocks in markdown documentation, you can use a CI/CD pipeline skill that parses Markdown files, executes the embedded Rugo code snippets, and verifies their compilation and output accuracy.

How does output verification work for Rugo code snippets in Markdown?

Output verification for Rugo code snippets works by executing the code block and comparing its actual output string against the expected text defined in a following markdown text block.

Can I check markdown code examples in a CI/CD pipeline to prevent documentation rot?

Yes, you can check markdown code examples in a CI/CD pipeline by running an automated validation process that compiles Rugo snippets and verifies their output, ensuring documentation remains accurate and functional.

What is the best way to ensure Rugo documentation examples still compile after language updates?

The best way to ensure Rugo documentation examples still compile after updates is to run an automated markdown validation tool that parses files and tests all embedded Rugo code blocks for compilation accuracy.

Do I need additional dependencies to verify Rugo code snippets in markdown files?

No additional dependencies are required to verify Rugo code snippets in markdown files, as this validation process operates standalone to parse markdown, execute Rugo code, and compare string outputs.