migrate-research

Iteratively update citum-migrate Rust code and validate against a priority style corpus.

31|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/citum/citum-core --skill migrate-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-research
Source: https://github.com/citum/citum-core/tree/main/.claude/skills/migrate-research
Command: npx skills add https://github.com/citum/citum-core --skill migrate-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Citum migration can produce formatting and data-mapping differences compared to high-fidelity reference outputs, and this Skill reduces that gap by running an evidence-driven loop of converter code changes and validation.

Core Features & Use Cases

  • Autonomous converter improvement loop: Iterates on Rust code in the citum-migrate crate to raise fidelity, measuring outcomes across a priority style corpus.
  • Failure-pattern clustering with classification: Groups observed mismatches into clusters, classifies root causes (converter vs. style vs. processor vs. adjudication), and targets fixes accordingly.
  • Evidence-based guardrails and reporting: Validates changes with cargo nextest, keeps improvements, and reverts failures while producing a decision-quality report.

Quick Start

Run the migrate-research workflow to iteratively enhance citum-migrate fidelity for the highest-priority migration issues until a stop or escalation verdict is reached.

Frequently Asked Questions about migrate-research

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

FAQPage Schema
How do I improve migration converter fidelity automatically in Rust?

To improve migration converter fidelity, this Skill iteratively updates Rust code and validates changes against a priority style corpus. It runs an evidence-driven loop that clusters mismatches, applies targeted fixes, and uses cargo nextest to retain improvements or revert failures.

What is the best way to group and classify migration mismatch root causes?

Grouping and classifying migration mismatch root causes is handled by clustering observed failures into distinct groups. The Skill classifies whether root causes originate from the converter, style, processor, or adjudication layers, enabling targeted code fixes based on the identified pattern.

Does the fidelity testing loop automatically revert failed converter code changes?

Yes, the fidelity testing loop automatically reverts failed converter code changes. It uses cargo nextest validation to evaluate each change attempt, permanently keeping improvements that pass while automatically reverting any modifications that fail the regression tests.

How do I validate converter code changes against a style corpus during migration?

Validating converter code changes against a style corpus requires running the full evidence loop. The Skill measures fidelity outcomes across the priority style corpus, uses cargo nextest for regression testing, and generates a decision-quality report to confirm if the changes should be kept or reverted.

Can I resume an interrupted automated regression testing session for migration styles?

Yes, you can resume an interrupted automated regression testing session for migration styles. The Skill supports repeated migration mismatch clustering and resume sessions, allowing you to continue the converter improvement loop across multiple styles until a stop or escalation verdict is reached.

Why does my migration output have formatting and data-mapping differences from the reference?

Migration output has formatting and data-mapping differences because the converter logic deviates from high-fidelity reference outputs. This Skill reduces that gap by applying an autonomous evidence-driven loop of converter code changes and validation against a priority style corpus to iteratively raise fidelity.