What problem does it solve? Keeping multiple consuming projects in sync with the latest version of a framework maintained in a private monorepo is error-prone manual work: copying files by hand, tracking which project has which version, and remembering to commit version bumps. This Skill automates the entire distribution lifecycle over the local filesystem. ## Core Features & Use Cases - Release lifecycle management: Prompts for a release type (major, minor, patch, or amend), bumps the version in package.json via npm, and commits the bump as a standalone git commit. - Per-target file distribution: Copies framework files to each registered consuming project using rsync, honoring per-project exclusions from .jenga_ignore and writing jenga.config.json atomically. - Dry-run safety gate: Previews every planned copy action per target and requires explicit user confirmation before writing any files. - Use Case: You maintain a framework monorepo and three client projects consume it. Run the distribute flow, choose "patch", review the dry-run output for all three targets, confirm, and each project receives the updated files plus an updated jenga.config.json while the version bump is committed automatically. ## Quick Start Ask the agent to distribute the framework to all registered consuming projects with a patch release, reviewing the dry-run preview before confirming.
