Agent Task Recipes

These recipes help coding agents make focused ChromoSort changes without guessing which files, tests, or docs should move together. Use them with AGENTS.md and the Agent Readiness Roadmap.

Shared First Steps

Before editing:

  1. Read AGENTS.md.
  2. Read the command page under docs/commands/ that matches the change.
  3. Search the relevant source module and tests with rg.
  4. Use synthetic fixtures under tests/data/ unless the task explicitly provides real data.

After editing, run the smallest focused check, then broaden to:

make agent-check

Pixi equivalent:

pixi run agent-check

Add Or Change A CLI Flag

Inspect:

Update:

Verify:

python3 tests/test_cli.py
python3 -m unittest discover -s tests -v

Add A TSV Output Column

Inspect:

Update:

Guardrail:

For review-event TSVs, preserve schema compatibility. Add new columns as explicit fields or discovered extras without breaking existing accepted rows.

Change A FASTA-Writing Command

Inspect:

Update:

Guardrail:

Every FASTA-changing command creates a new coordinate system. Preserve the rule that downstream alignment-dependent commands need fresh coords or PAF for that exact FASTA.

Change The Review-Event Schema

Inspect:

Update:

Guardrail:

Accepted reviewed rows must be revalidated against the current FASTA, assignment, graph, and command settings before sequence changes are applied.

Change Plotting Or Manual Dashboard Behavior

Inspect:

Update:

Verify:

python3 tests/test_plot.py
python3 tests/test_manual.py

Add Graph, GAF, Or Long-Read Evidence Fields

Inspect:

Update:

Guardrail:

Keep evidence authority explicit. GFA, GAF, long-read PAF, Hi-C-like contacts, reference-placement PAF, and patch tables are not interchangeable, and most are review or branch-support evidence rather than direct sequence-edit authority.

Docs-Only Change

Inspect:

Verify:

git diff --check

If Ruby/Bundler is available:

make docs-check