jade-recipe-noop

Mark JADE migration findings as SKIPPED or DEFERRED without source transforms.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill handles migration rules that do not require a source change, preventing the pipeline from stalling on informational findings and keeping batch progress deterministic.

Core Features & Use Cases

  • No-op fallback handling: Marks applicable flagged lines as SKIPPED when a dedicated transform is unnecessary or already complete.
  • Deferred routing: Preserves unresolved rules as DEFERRED when a transform is expected but no recipe exists yet.
  • Migration hygiene: Supports JADE rule dispatch workflows where some checks are advisory, such as already-supported Java 6 behavior or previously migrated changes.

Quick Start

Use the jade-recipe-noop skill to classify the flagged file at the specified line as SKIPPED when the rule is informational.

Frequently Asked Questions about jade-recipe-noop

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

FAQPage Schema
How do I skip informational migration findings without applying a source transform?

To skip informational migration findings, you can use a no-op fallback dispatcher to mark flagged files as SKIPPED, preventing the pipeline from stalling on advisory checks that require no code changes.

What is the difference between SKIPPED and DEFERRED outcomes in JADE recipe dispatch?

In JADE recipe dispatch, SKIPPED marks informational findings or already-resolved changes as complete, while DEFERRED preserves unresolved rules when a transform is expected but no recipe exists yet.

When do I need a no-op fallback for Java 1.5 to 1.6 migration rules?

You need a no-op fallback for Java 1.5 to 1.6 migration when rules are advisory, involve already-supported Java 6 behavior, or represent previously migrated changes that require no source transform.

Can I use a no-op dispatcher to keep batch migration progress deterministic?

Yes, a no-op dispatcher keeps batch migration progress deterministic by classifying flagged lines with deterministic SKIPPED or DEFERRED outcomes and preserving rule-specific context via the manifest entry.

What are the limitations of using a no-op fallback for migration rule dispatch?

The no-op fallback is limited to informational or already-resolved findings; it cannot apply source transforms for unresolved rules, which remain DEFERRED until a dedicated recipe is created.

Why does my migration pipeline stall on advisory compatibility findings?

Migration pipelines stall on advisory compatibility findings when no dedicated transform exists; a no-op fallback resolves this by marking the flagged file and line reference as SKIPPED to continue batch processing.