Files
ECC/pi/core
Tomoya.FujitaandClaude Fable 5.1 aa63399ebd feat(skills): add issue-review skill and /issue-review command
Add a GitHub issue counterpart to the PR mode of /code-review. The
canonical workflow lives in skills/issue-review and walks nine phases:
fetch the issue with gh, build project context, classify type and
completeness, verify the claim against the code at HEAD, search for
duplicates and prior fixes, assess severity and decision, write a
review artifact with a draft reply, publish only on explicit flags,
and print a one-screen summary.

Issue text is treated as untrusted data: embedded instructions are
never followed, pasted code is never run, and arbitrary links are not
fetched. Writing to GitHub is opt-in via --comment or --label and the
workflow never closes, reopens, or assigns issues.

commands/issue-review.md is the thin slash-command shim. The new
structural test guards the frontmatter, required sections, phase
order, safety invariants, and registration on every surface.

Register the skill and command in package.json, agent.yaml, the
operator-workflows install module, the quick reference, the
command-agent map, and the README; regenerate the command registry
and sync catalog counts to 312 skills and 98 commands.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Tomoya.Fujita <fujita.tomoya@triorb.co.jp>
2026-10-29 09:23:41 +09:00
..

ecc-pi-core

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