internationalcolorconsortium/iccdev/icc2-xml-spec-qa

ICC.2 XML Specification QA

Use this skill when changing ICC.2 header XML parsing, spectral or bi-spectral signatures and ranges, MCS handling, or the related command-line QA surface.

Workflow

1. Keep builds and generated evidence outside the source worktree. Do not add a

standalone C++ PoC; use the native checked-in XML inputs and existing tools.

1. Read docs/xml-spec-qa.md and inspect the applicable ICC.2 clauses, encoding

tables, and formulae before changing an expected value or required child.

1. Build iccFromXml, iccToXml, iccDumpProfile, iccRoundTrip, and

iccPawgReport with tests enabled.

1. Run .github/scripts/iccdev-xml-spec-qa.sh with ICCDEV_TOOLS_DIR and an

isolated ICCDEV_TEST_OUTDIR.

1. Require exact signatures, wavelength ranges, channel counts, XML fidelity,

required element payloads, expected negative diagnostics, and no sanitizer finding. For a field the binary encoding requires, omit its XML child explicitly and require parser-level rejection with no output rather than a default or uninitialized serialized value.

1. Treat iccRoundTrip unsupported-profile results as capability evidence, not

successful transforms. Treat ICC.2 PAWG assessment failures as review data until its rule set is ICC.2-aware; require JSON parse evidence regardless.

1. Discover and run iccdev.xml-spec-qa with CTest. For spectral MPE parser

changes, also run iccdev.spectral-clut-xml-channel-mismatch. Report the compiler, sanitizer envelope, profile inputs, complete pass count, and output path.

Do not commit generated profiles, round-trip XML, JSON reports, logs, profraw, or coverage HTML. If an XML specification contract changes, update the native fixture, script, CTest coverage, prompt/agent guidance, and this document together.