affaan-m/ecc

ecc-contribution-review

Prepare an ECC skill contribution for review by organizing repository, install-surface, cross-harness, validation, security, and commit observations into a local proposal.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/affaan-m/ecc --skill ecc-contribution-review

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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

  1. Start from the active ECC checkout. Record the branch, base and head, package

lock, install manifests, catalog generator, skill placement policy, and a checkpoint.

  1. Identify the canonical source under skills/ for curated workflows. Keep

generated, learned, and imported content outside shipped sources.

  1. 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.

  1. Run the required validators and tests separately. Record exact commands,

results, and evidence. The compiler does not execute them.

  1. 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:

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/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.

  1. 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.

  1. 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.

dallo stesso repository

Altri Skills

Tutti gli Skills
affaan-m
Community

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Installazioni / 24h
489
GitHub Stars
308,2K
Aggiornato
20 nov
affaan-m
Community

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

Installazioni / 1h
5
GitHub Stars
308,2K
Aggiornato
20 nov
affaan-m
Community

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Installazioni / 1h
2
GitHub Stars
307,9K
Aggiornato
20 nov
affaan-m
Community

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Installazioni / 1h
2
GitHub Stars
307,9K
Aggiornato
20 nov