Files
ECC/pi/core/README.md
T
Affaan MustafaandGitHub c70874fae9 feat(pi): curated pi/core skills+prompts profile, CI load test, and 2.2.2 release sync (#3264)
Adds a curated, Pi-native, skills+prompts-only profile at pi/core/ for downstream packagers that mirror GitHub Releases.

- manifests/pi-core.json: explicit include lists, per-item exclusion reasons, curation rules, safety allowlists; every root skill and command must be classified.
- scripts/build-pi-core.js regenerates pi/core deterministically (package.json from VERSION, LICENSE, README.md, CURATION.md, skills/, commands/); --check fails CI on drift. council is renamed ecc-council inside pi/core only.
- Safety checks: no callable endpoints outside the allowlist, no npx/curl|sh/pip install, no secrets, no absolute home paths, no symlinks, valid frontmatter, no duplicate names.
- CI: build + drift check and an offline Pi CLI load test of pi/core.
- Release: VERSION, package.json and pi/core/package.json at 2.2.2, CHANGELOG, tag-triggered release verification, and a two-week cadence in CONTRIBUTING.md.

pi/core: 123 of 293 skills and 24 of 94 commands; 35,006 characters of skill description text.
2026-09-29 20:24:05 -05:00

1.1 KiB

ecc-pi-core

A curated, Pi-native profile of ECC (Everything Claude Code): 123 portable engineering skills and 24 pure prompt-workflow commands, with no extensions, no hooks, no runtime downloads, and no network or SaaS dependencies.

Contents

  • skills/ - language, framework, testing/TDD, code review, security review, planning, refactoring, docs, and git/PR workflow skills.
  • commands/ - prompt commands that are pure prompt workflows.
  • CURATION.md - every excluded skill and command with its reason.

Use

Copy this directory into your project (or pin a release tarball) and load it with the Pi coding agent:

pi --no-extensions --extension pi/core

Offline load test (as run in CI):

PI_OFFLINE=1 pi --offline --mode rpc --no-session --no-context-files --no-extensions \
  --extension pi/core </dev/null >/dev/null

Regenerate

pi/core is generated from manifests/pi-core.json and committed so release tarballs contain it verbatim. After changing the manifest or any included source content, run:

node scripts/build-pi-core.js

and commit the result. CI verifies the committed profile is up to date.