Update: adopt SpecSync 5 and Trust 1#14
Conversation
There was a problem hiding this comment.
Code Review
This pull request adopts SpecSync 5.0.1 and Trust 1.0.0 governance for the GitHub Fledge plugin, introducing canonical specs, companion files, migration change records, task definitions, and IDE skill commands. The review feedback suggests removing redundant empty headings in the skill markdown files, correcting split acceptance criteria in the migration change files, and expanding the smoke test and verification commands to cover all fledge-github sub-executables instead of only the main dispatcher.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f5ee59c46f
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
bin/fledge-github*command.Test Plan
fledge lanes run verify— ShellCheck, Bash syntax, and all-executable offline help smoke passspecsync check --strict --forcepasses at the committed advisory thresholduser:0xLeifBlocker
All six implementation files are extensionless Bash executables. SpecSync 5.0.1 does not discover extensionless files through its supported language extensions, so it reports
0/0coverage;--require-coverage 100correctly rejects that vacuous result. The PR remains draft until SpecSync supports shebang/extensionless discovery and the repository can enforce a truthful 100% threshold. No wrapper or product-script rename is included in this migration.Authenticated GitHub reads and mutations remain independently authorized and are intentionally excluded from the offline migration lane.