parser-velocity

Batch parser-gap edits into a single cargo test compile cycle.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gamajose/MagicTheGathering --skill parser-velocity
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: parser-velocity
Source: https://github.com/gamajose/MagicTheGathering/tree/main/.claude/skills/parser-velocity
Command: npx skills add https://github.com/gamajose/MagicTheGathering --skill parser-velocity

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This skill accelerates parser development by batching edits and deferring the full gate process to the end of a session, enabling rapid iteration on near-miss cards without rebuilding after every small change.

Core Features & Use Cases

  • Batch edits to avoid per-card compilation, cutting cycle time from minutes to seconds.
  • Focused on parser-gap issues across A/B/C categories, surfacing actionable changes while preserving the existing nom combinator structure.
  • Integrates with the Phase 1 batch workflow and the oracle-gen validation to preserve stable parsing behavior across sessions.

Quick Start

Batch 5–10 parser edits and run the full gate only at session end.

Frequently Asked Questions about parser-velocity

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

FAQPage Schema
How do I batch parser edits to avoid recompiling after every change?β–Ό

Batch parser edits by grouping 5–10 near-miss card fixes into a single compile cycle, running one cargo test per batch. This defers full gates like fmt, clippy, and coverage to session end, cutting iteration time from minutes to seconds.

What is the best way to speed up parser development sprints using nom combinators?β–Ό

Accelerate parser development sprints by batching edits across A/B/C category cards and preserving existing nom combinator structures. This approach enforces a deterministic workflow that defers full gate checks to the end of the session.

Do I need jq installed to batch parser-gap fixes in a development workflow?β–Ό

Yes, you need jq version 1.6 or higher installed as a prerequisite. The batch parser-gap workflow enforces deterministic prereqs and relies on jq to process near-miss parser cards before grouping them into a single compile cycle.

Can I defer formatting and clippy checks to the end of a parser development session?β–Ό

Yes, you can defer full gates including fmt, clippy, tests, and coverage to the session end. By batching 5–10 parser edits into a single cargo test run, you maintain rapid iteration cycles without rebuilding after every small change.

Why does my parser iteration slow down when running cargo test after every edit?β–Ό

Parser iteration slows down because per-card compilation rebuilds the project after each small change. Batching 5–10 edits into a single compile cycle and deferring full gates to session end reduces cycle time from minutes to seconds.

When should I avoid deferring full gates during parser development?β–Ό

Avoid deferring full gates when you need immediate validation of formatting, clippy, or coverage changes. This batching approach is designed for near-miss parser cards in Phase 1 batch workflows where preserving stable parsing behavior across sessions is the priority.