ECC Skill Contribution Review Packet
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.
Workflow
Start from the active ECC checkout. Record the branch, base and head, package
lock, install manifests, catalog generator, skill placement policy, and a
checkpoint.
Identify the canonical source under skills/ for curated workflows. Keep
generated, learned, and imported content outside shipped sources.
Record the change intent, artifact graph, install coverage, harness copies,
catalog and registry counts, test phases, coverage, security review,
budgets, and commit proposal with evidence references.
Run the required validators and tests separately. Record exact commands,
results, and evidence. The compiler does not execute them.
Copy the template, then edit the copy to replace every placeholder with
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:
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/compile_contribution_review.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.
Review every reported contradiction and semantic page fault. The compiler
returns require_review for structurally valid input and never approves a
contribution. It does not prove that supplied claims are true or CI passed.
Recompile after changes to HEAD, policy, manifests, catalog, adapters, tests,
coverage, security findings, or review evidence.
Local Contract
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. The JSON input is an
illustrative fixture, not a current repository observation.
1---2name: ecc-contribution-review3description: Prepare an ECC skill contribution for review by organizing repository, install-surface, cross-harness, validation, security, and commit observations into a local proposal. Use when preparing a skill contribution for review.4metadata:5 source: https://skillmd.com/skills/affaan-m/ecc-contribution-review6 origin: ECC7---89# ECC Skill Contribution Review Packet1011Use this workflow to prepare skill contribution observations for maintainer review.12This version supports `changeKind: "skill"` with canonical source under `skills/`.13It compiles supplied observations; it does not independently inspect Git,14files, CI, test results, coverage, or referenced evidence. Treat every imported15claim as unverified until a reviewer checks its evidence.1617## Workflow18191. Start from the active ECC checkout. Record the branch, base and head, package20 lock, install manifests, catalog generator, skill placement policy, and a21 checkpoint.222. Identify the canonical source under `skills/` for curated workflows. Keep23 generated, learned, and imported content outside shipped sources.243. Record the change intent, artifact graph, install coverage, harness copies,25 catalog and registry counts, test phases, coverage, security review,26 budgets, and commit proposal with evidence references.274. Run the required validators and tests separately. Record exact commands,28 results, and evidence. The compiler does not execute them.295. Copy the template, then edit the copy to replace every placeholder with30 current observations and references to evidence you gathered. The template31 is intentionally incomplete and must not be treated as an observation.32 After editing it, compile the packet:3334 ```bash35 mkdir -p .memory-kit36 cp skills/ecc-contribution-review/templates/contribution-review-observation.json \37 .memory-kit/contribution-review-observation.json38 python3 skills/ecc-contribution-review/scripts/compile_contribution_review.py \39 .memory-kit/contribution-review-observation.json \40 --output .memory-kit/ecc-contribution-review.json41 ```4243 `--output` writes a new capsule file in the existing parent directory and44 refuses to overwrite any existing path. The compiler does not create45 directories, modify source files, run tests, update catalogs, commit, push,46 or open a pull request. Exit code 0 means a packet was emitted without47 reported faults or contradictions; review is still required. Exit code 248 means validation faults, contradictions, or an input/output error. A49 diagnostic packet may still be emitted with exit code 2. Inspect the packet50 and stderr; the exit code alone does not establish whether output exists.51526. Review every reported contradiction and semantic page fault. The compiler53 returns `require_review` for structurally valid input and never approves a54 contribution. It does not prove that supplied claims are true or CI passed.557. Recompile after changes to HEAD, policy, manifests, catalog, adapters, tests,56 coverage, security findings, or review evidence.5758## Local Contract5960The packet describes source ownership, generated-root exclusion, install61coverage, normalized harness identity, catalog reconciliation, TDD claims,62security review, validation gates, and a conventional-commit proposal. Runner63proposals are typed argument arrays and remain unexecuted. All generated64authority and external effects remain false.6566See [the workflow](docs/WORKFLOW.md), [the design](docs/DESIGN.md), and [the67contract](references/contribution-review-contract.md). The JSON input is an68illustrative fixture, not a current repository observation.