jade-core-batch-processor

Build per-rule file batches from flag and queue indexes with atomic JSON writes.

1|Updated Apr 14, 2026

Search Tags:#batch-processing #status-tracking #migration-pipeline #jade #sequential-batching #json-artifacts

Ready to run

npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-batch-processor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jade-core-batch-processor
Source: https://github.com/TheRealSeber/PolishedJADEite/tree/main/.claude/skills/jade-core-batch-processor
Command: npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-batch-processor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents JADE migration work from becoming a loosely coordinated pile of per-file edits by enforcing a single-rule batch workflow with explicit status tracking and resumable state.

Core Features & Use Cases

Single-rule batching: Builds and manages exactly one rule_id batch at a time so the orchestrator never processes multiple modernization rules in parallel.
Per-file task tracking: Groups flagged entries by file, assigns statuses, and persists progress so interrupted migrations can resume safely.
Operational coordination: Writes batch artifacts and aggregate status files to keep downstream verification and commit steps aligned with the current rule.
Use Case: When a migration run flags dozens of files for the same modernization rule, this Skill prepares the file task list, updates completion state after each file, and helps the orchestrator stop or continue cleanly.

Quick Start

Use the jade-core-batch-processor skill to prepare the next rule batch from the current flag index and keep file-level batch status synchronized until the rule is complete.

Frequently Asked Questions about jade-core-batch-processor

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

FAQPage Schema

How do I process one migration rule at a time during a JADE migration?▼

To process one migration rule at a time, you build a single-rule batch from the flag index and track file-level completion state. This ensures the orchestrator processes, verifies, and commits exactly one rule_id before starting the next.

What is the best way to track per-file status during a sequential migration pipeline?▼

Per-file status tracking during a migration pipeline involves grouping flagged entries by file, assigning statuses, and persisting progress. This approach writes atomic JSON artifacts so interrupted sequential batching runs can resume safely.

How does sequential batching handle interrupted migration pipelines?▼

Sequential batching handles interruptions by enforcing per-file status tracking and atomic JSON artifact writes. It persists completion state for each flagged file, allowing the migration pipeline to resume cleanly from the last committed rule batch.

Do I need specific JSON artifacts to start single-rule batching for migration?▼

Yes, single-rule batching requires 04-flag-index.json and 05-rule-queue.json as inputs. These JSON artifacts provide the flagged file entries and rule queue sequence needed to build the current batch and apply strict validation.

Why should migration rules be processed sequentially instead of in parallel?▼

Migration rules should be processed sequentially to prevent loosely coordinated per-file edits. Sequential batching with strict validation and atomic writes keeps downstream verification and commit steps aligned with the current rule.

Can I use batch processing for tracking completion state across dozens of flagged files?▼

Yes, batch processing tracks completion state across dozens of flagged files by grouping entries, assigning statuses, and writing aggregate status files. This keeps downstream verification aligned until the entire rule batch is complete.