Repository navigation
feat: package shared Codex Workflow as a skills-only plugin - #3
Merged
Merged
Conversation
9 of 10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Package the portable workflow as one skills-only ChatGPT/Codex plugin maintained in this repository. Six focused skills provide workflow/planning, project setup, PR/CI, test audit, docs gardening and complexity judgment. Conditional references replace the old standard documents; project integration stages only essential guidance and optional roles rather than copied workflow editions.
The setup skill preserves project policy and existing adaptations. Projects retain their own contracts, commands, CI gates and operational procedures. Packaging excludes private evidence and requires no runtime server or connector.
Validation
Scope
This changes workflow packaging and integration tooling. It does not change any consumer runtime, CI gate, release/deployment policy or personal configuration. Historical case studies and role defaults remain preserved.