test-demos

Identify changed files and generate a Claude Code test execution plan.

2|Updated Apr 7, 2026

Search Tags:#testing #manual-testing #r-scripts #test-demos #demo-plans #branch-change-analysis

Ready to run

npx skills add https://github.com/soumyaray/ray-ai-skills --skill test-demos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-demos
Source: https://github.com/soumyaray/ray-ai-skills/tree/main/ray-test-demos
Command: npx skills add https://github.com/soumyaray/ray-ai-skills --skill test-demos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze branch changes for test gaps and plan automated/demo-based reviews to ensure coverage.

Core Features & Use Cases

Identify changed files on a branch and map them to existing unit tests and demo scripts.
Cross-reference unit tests and demo scripts to surface coverage gaps and generate a structured PLAN.demo-manual-tests.md.
Provide a reproducible, executable plan for Claude Code to validate changes across workflows.

Quick Start

Run this skill on the current branch to generate PLAN.demo-manual-tests.md for Claude Code to execute.

Frequently Asked Questions about test-demos

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

FAQPage Schema

How do I plan demo-based manual tests for code changes on a branch?▼

To plan demo-based manual tests, you need to identify changed files on the active branch and map them to existing test coverage data. This process surfaces untested paths by cross-referencing unit tests and demo scripts to generate a structured test plan.

What is a demo-manual-tests plan and when do I need it?▼

A demo-manual-tests plan is a reproducible markdown file containing verification steps and plot-check guidance for validating code changes. You need it when you want Claude Code to execute structured, demo-based reviews to ensure your branch changes have proper test coverage.

How do I find test coverage gaps for changed files on my current branch?▼

You find test coverage gaps by cross-referencing your changed files against existing unit tests and demo scripts. This analysis surfaces untested paths and produces a structured plan that includes verification steps to validate the modified workflows.

Can I generate a reproducible test plan for Claude Code to execute automatically?▼

Yes, you can generate a reproducible PLAN.demo-manual-tests.md file for Claude Code to execute. The plan includes verification steps and plot-check guidance derived from analyzing the test coverage gaps on your active branch.

Does this approach work without any external dependencies or components?▼

Yes, this approach works without external dependencies or components because it analyzes your active branch directly. It maps changed files to existing test coverage data and produces a self-contained markdown plan for Claude Code execution.

What's the best way to surface untested paths in modified R scripts?▼

The best way to surface untested paths in modified R scripts is to cross-reference the changed files with existing unit tests and demo scripts. This analysis identifies coverage gaps and generates a structured plan with verification steps to validate the untested code.