Files
ECC/pi/core
Affaan MustafaandGitHub 0348d7b6d7 chore(release): 2.2.3, ECC-only naming in pi/core and a longer npm publish wait (#3329)
pi/core and the bundled blueprint skill now refer to the project as ECC only;
the generated README no longer expands the name. Profile contents, package
name and paths are unchanged (123 skills, 24 commands).

The release workflows poll npm for up to five minutes after publish before
verifying the artifact. In 2.2.2 the check gave up after about 30 seconds while
npm was still processing, failing the run before latest was promoted and the
GitHub Release was created.

Version metadata synced to 2.2.3 with CHANGELOG, translated release headings
and release notes; skill-triggers registryDigest updated for the blueprint text.
2026-10-01 17:49:51 -05:00
..

ecc-pi-core

A curated, Pi-native profile of ECC: 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.