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.
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.cursor/skills/ecc-contribution-review/SKILL.mdThe canonical home for this skill is ecc-contribution-review in affaan-m/ECC
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.
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.
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.
affaan-m/ECC
3f14a10
Canonical home
since Nov 19, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.