Use this workflow to prepare skill contribution observations for maintainer review.
This version supports changeKind: "skill" with canonical source under skills/.
It compiles supplied observations; it does not independently inspect Git,
files, CI, test results, coverage, or referenced evidence. Treat every imported
claim as unverified until a reviewer checks its evidence.
lock, install manifests, catalog generator, skill placement policy, and a
checkpoint.
skills/ for curated workflows. Keepgenerated, learned, and imported content outside shipped sources.
catalog and registry counts, test phases, coverage, security review,
budgets, and commit proposal with evidence references.
results, and evidence. The compiler does not execute them.
current observations and references to evidence you gathered. The template
is intentionally incomplete and must not be treated as an observation.
After editing it, compile the packet:
```bash
mkdir -p .memory-kit
cp skills/ecc-contribution-review/templates/contribution-review-observation.json \
.memory-kit/contribution-review-observation.json
python3 skills/ecc-contribution-review/scripts/compilecontributionreview.py \
.memory-kit/contribution-review-observation.json \
--output .memory-kit/ecc-contribution-review.json
```
--output writes a new capsule file in the existing parent directory and
refuses to overwrite any existing path. The compiler does not create
directories, modify source files, run tests, update catalogs, commit, push,
or open a pull request. Exit code 0 means a packet was emitted without
reported faults or contradictions; review is still required. Exit code 2
means validation faults, contradictions, or an input/output error. A
diagnostic packet may still be emitted with exit code 2. Inspect the packet
and stderr; the exit code alone does not establish whether output exists.
returns require_review for structurally valid input and never approves a
contribution. It does not prove that supplied claims are true or CI passed.
coverage, security findings, or review evidence.
The packet describes source ownership, generated-root exclusion, install
coverage, normalized harness identity, catalog reconciliation, TDD claims,
security review, validation gates, and a conventional-commit proposal. Runner
proposals are typed argument arrays and remain unexecuted. All generated
authority and external effects remain false.
See the workflow, the design, and [the
contract](references/contribution-review-contract.md). The JSON input is an
illustrative fixture, not a current repository observation.