source-command-implement-batch

Orchestrate parallel card implementation from LEGACY_CARD_MAP.csv with concurrency capped at 5.

Updated May 14, 2026
One-click install
npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-implement-batch-chroniicallydiistracted
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-implement-batch
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.agents/skills/source-command-implement-batch
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-implement-batch-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates batch execution of migrated card implementation work so multiple card implementations can run concurrently while sharing a single source-of-truth input list.

Core Features & Use Cases

  • Single source of truth: Reads packages/lorcana/lorcana-cards/src/cards/LEGACY_CARD_MAP.csv and treats it as authoritative for what to implement next.
  • Rolling-window concurrency: Launches up to 5 card implementation sub-agents in parallel and continuously backfills as agents finish.
  • Deterministic assignment & progress signaling: Assigns non-overlapping tail rows to agents (immutable offsets) and removes processed lines from the CSV so the batch progresses autonomously.
  • Robust per-agent reporting: Collects structured per-card outcomes (implemented, already-done, skipped-vanilla, failed) and continues even when some cards fail.
  • CI batching discipline: Ensures only the orchestrator runs the broader bun run ci-check after all agents finish, while each sub-agent runs a filtered test for its card.

Quick Start

Run /source-command-implement-batch with default tail size to migrate the last 10 non-vanilla rows from LEGACY_CARD_MAP.csv using up to 5 parallel agents.

Frequently Asked Questions about source-command-implement-batch

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

FAQPage Schema
How do I parallelize batch processing for code migration from a CSV file?

Batch processing for code migration is parallelized by parsing CSV rows and launching up to 5 concurrent sub-agents. The orchestrator assigns non-overlapping tail rows to each agent, ensuring safe parallel execution while continuously backfilling as agents finish their work.

What is tail-based batch migration and how does it track progress?

Tail-based batch migration processes the last rows of a CSV file by assigning immutable offsets to agents and removing processed lines upon completion. Removing processed lines from the source-of-truth CSV signals progress autonomously and prints a continuation command for the next batch.

How do I run multiple agent workflows concurrently without overlapping work allocation?

Multiple agent workflows run concurrently by assigning immutable row offsets from a single CSV input to each sub-agent. This deterministic assignment ensures non-overlapping work allocation, while the orchestrator aggregates structured per-agent reports including implemented, already-done, skipped-vanilla, and failed statuses.

Can I configure concurrency limits for automated card implementation testing?

Concurrency limits for automated card implementation are capped at 5 parallel sub-agents. Each sub-agent runs a filtered test for its specific card, while the orchestrator executes the broader CI check only after all agents finish to maintain batching discipline.

What happens when a sub-agent fails during parallel code migration?

When a sub-agent fails during parallel code migration, the orchestrator logs the failure as a structured per-card outcome and continues processing the remaining batch. The system aggregates all agent reports, allowing successful migrations to complete even when individual cards fail.