Contributing to Pocketto on GitHub

How the Pocketto repository is organized, the source-of-truth rules, and where to contribute to this MIT-licensed project on GitHub.

Pocketto is MIT-licensed and developed in the open at github.com/rfxlamia/pocketto.

Repository organization

Path	What lives there
`skills/<name>/`	One directory per skill: `SKILL.md` (the canonical definition), `references/` (deep protocols loaded on demand), bundled `.skill` archives, optional `.skillkit-mode`
`cli/commands/`, `cli/lib/`	The `pocketto-pi` CLI: eager Core commands plus the lazy `mode`/`format` Enterprise commands
`enterprise/`	The Enterprise adapter: registration, preflight, dispatch, issue/phase/closure handlers
`test/`, `test-support/`	`node:test` suites covering CLI, lifecycle, surfaces, Enterprise, and documentation
`scripts/build-surfaces.js`	Stages a release role from the `surfaces.json` manifest
`surfaces.json`	The four-role manifest with includes, forbidden paths, ownership, and the CLI boundary
`assets/`	The pipeline diagram (`pipeline.svg` + Excalidraw source)
`docs/pocket/`	Pocketto's own dogfooded artifacts: real specs, plans, execution logs, and closeout journals produced by the pipeline itself
`.claude-plugin/`	The Claude Code marketplace and plugin manifests
`llms.txt`, `README.md`, `CHANGELOG.md`, `AGENTS.md`	Top-level documentation and the Enterprise mode block

SKILL.md files are canonical for skill behavior. Bundled .skill archives are derived: rebuild them with rebuild-skills.sh after editing skills (the changelog documents this script's role in keeping archives in sync).
The contract files are cited, not restated. pocket-development's SKILL.md deliberately cites two-stage-review.md and phase-level-pass.md rather than duplicating their rules. Duplicated rules drift.
surfaces.json governs packaging. Any change that adds, moves, or re-owns files must update the manifest's includes, ownership, and (where relevant) forbidden_paths/forbidden_content.

Bugs and features: GitHub issues.
Changes: pull requests against the repository. CHANGELOG.md documents every release. Notable changes belong there.
The documentation you are reading is built from the repository's public contract; when behavior changes, the docs' claims change with it.

MIT. See the LICENSE file in the repository.