jade-recipe-dummy

Append an E2E TEST comment to a specified line in a source file.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-recipe-dummy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jade-recipe-dummy
Source: https://github.com/TheRealSeber/PolishedJADEite/tree/main/.claude/skills/jade-recipe-dummy
Command: npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-recipe-dummy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a safe end-to-end test target for the migration pipeline when you need to confirm that rule dispatch, file editing, and success reporting all work together.

Core Features & Use Cases

  • E2E Validation: Applies a harmless comment change to a flagged line so the pipeline can prove it touched the correct file.
  • Dispatcher Compatibility: Accepts a file path and line number, matching the interface expected by the rule dispatcher.
  • Deterministic Output: Returns structured JSON describing the result, making it easy to verify success or failure in automated tests.
  • Use Case: Use it to smoke-test a fresh deployment before running real JADE migration recipes.

Quick Start

Use the jade-recipe-dummy skill to append the E2E TEST comment to the specified line in the target file.

Frequently Asked Questions about jade-recipe-dummy

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

FAQPage Schema
How do I validate end-to-end pipeline file editing without modifying actual logic?▼

End-to-end pipeline validation can be performed by appending a harmless E2E TEST comment to a matched line in a source file. This deterministic file replacement confirms the pipeline touched the correct file without altering operational code.

What is a safe target for smoke-testing rule dispatcher integration checks?▼

A safe target for rule dispatcher integration checks uses a dummy recipe that accepts a file path and 1-based line number. It performs a controlled in-place edit and emits structured JSON status for automated verification.

How do I perform a deterministic file replacement for automated test migrations?▼

Deterministic file replacement for automated test migrations requires a file path and a 1-based line number to append a comment. The process outputs structured JSON describing the result, making it easy to verify success or failure.

Does the JADE migration pipeline support structured JSON status output for E2E validation?▼

The JADE migration pipeline supports E2E validation by emitting structured JSON status output after a controlled test migration. This verifies that rule dispatch and file editing work together correctly before running real recipes.

When should I use a dummy recipe for pipeline validation instead of real migration recipes?▼

A dummy recipe for pipeline validation should be used to smoke-test a fresh deployment before running real JADE migration recipes. It proves the pipeline can safely perform a harmless in-place edit on a flagged line.