Skip to content

refactor(skills): move FLOW skill distribution to jiggy/skills - #8

Open
zvictor wants to merge 1 commit into
mainfrom
codex/centralize-skills
Open

zvictor wants to merge 1 commit into
mainfrom
codex/centralize-skills

Conversation

@zvictor

@zvictor zvictor commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Why

Generated reference copies and skill-specific synchronization jobs make source PRs larger and couple documentation edits to generated-file conflicts. This follows Jig #84 by moving the public skill and its generation machinery into a shared repository.

Changes

  • Remove the public skills/ bundle, duplicate builder/tests, source-PR synchronization workflow, Just recipes, and local freshness gate. The central builder preserves FLOW's selected documentation, machine bytes, examples, and license notices without the old per-file checksum manifest.
  • Keep canonical FLOW documentation, independent package builds, repository development skills, and their separately needed dependencies.
  • Point installation to npx skills add jiggy/skills --skill flow.
  • Remove obsolete public-skill scanning and documentation-baseline plumbing; retain ordinary PR/push documentation comparisons.
  • Add the main-only shared notifier and update its workflow contracts and owning instructions.

Coordination and operation

The installable skills now live in jiggy/skills. That repository owns one source registry, builder, source revision lock, test suite, and reusable notification workflow for Bonsai, FLOW, and Jig. Its initial CI and refresh runs pass.

The source notifier runs only for this repository's main branch, has no checkout and no GITHUB_TOKEN permissions, and pins the shared workflow to d1277d5c5fb48f1c148a08e9131e7cf0d674ab0e. Immediate source-updated dispatch uses optional SKILLS_DISPATCH_TOKEN, a fine-grained token scoped to jiggy/skills with Contents: write. Central hourly/manual reconciliation works without that secret. No new credential was created as part of this migration.

The central receiver treats notifications only as a wake-up. It resolves the approved repositories' current main revisions itself, runs central tooling against inert source checkouts, and publishes only generated reference directories and the source lock. Authored skill changes remain reviewed changes in the central repository.

The central repository is already published, so this PR can merge independently of Bonsai and Jig. The generated source snapshot will update after this PR merges.

Validation

  • Central suite: 33 passed; generated FLOW reference bytes match the previous bundle apart from removal of obsolete provenance.
  • FLOW workflow contracts: 6 passed, including the final immutable notifier pin and main-branch guard.
  • Documentation checker: 39 documents, zero findings.
  • Modified-script syntax and whitespace checks pass.
  • The broader local Node tooling run had two failures in unchanged directory-promotion race tests; both reproduced against original-main script/test copies.
  • Bun 1.3.3 aborts before executing scripts in this environment, including a trivial script; native Bun docs tests and the fresh site build therefore await GitHub CI.

Signed-off-by: Victor Duarte <181076+zvictor@users.noreply.github.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-04T06:56:40.791857Z 6ace778 PR opened
🔒 Security Review ✅ Completed 2026-11-04T06:59:46.366670Z 6ace778 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant