Add machine-readable plugins.json with sync validation#9
Merged
Conversation
- Generate plugins.json from README.md Community Plugins section - Include name, url, owner, repo, description, category, install_url - Add scripts/generate_plugins_json.py to regenerate from README - Add CI workflow to fail if plugins.json drifts from README
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a plugins.json registry and a Python script to automate its generation by parsing the README.md file. The review identifies that the committed plugins.json contains a future date for last_updated, which is inconsistent with the generation script. Additionally, the script hardcodes the 'main' branch in installation URLs, potentially breaking for repositories using 'master', and the datetime import should be moved to the top level to comply with PEP 8.
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "name": "awesome-codex-plugins", | ||
| "version": "1.0.0", | ||
| "last_updated": "2026-03-30", |
| "description": m.group(5).strip(), | ||
| "category": current_category, | ||
| "source": "awesome-codex-plugins", | ||
| "install_url": f"https://raw.githubusercontent.com/{owner}/{repo}/main/.codex-plugin/plugin.json", |
|
|
||
|
|
||
| def main(): | ||
| import datetime |
| end = i | ||
| break | ||
|
|
||
| if start is None or end is None: |
| on: | ||
| pull_request: | ||
| paths: | ||
| - README.md |
| "description": m.group(5).strip(), | ||
| "category": current_category, | ||
| "source": "awesome-codex-plugins", | ||
| "install_url": f"https://raw.githubusercontent.com/{owner}/{repo}/main/.codex-plugin/plugin.json", |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Previous Issues — All Resolved
Files Reviewed (2 files)
Reviewed by mimo-v2-pro-20260318 · 91,301 tokens |
- Move import datetime to top-level imports (PEP 8) - Fix end-is-None false negative when Community Plugins is last section - Add TODO for install_url default branch assumption - Add generator script to CI paths trigger
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.
Adds `plugins.json` for easy programmatic consumption by registries and tooling.
What:
Why:
The HOL registry and other consumers need a structured data source. This keeps it single-source-of-truth with the README.
Schema:
```json
{
"name": "awesome-codex-plugins",
"version": "1.0.0",
"last_updated": "2026-03-30",
"total": 19,
"categories": ["Development & Workflow", "Tools & Integrations"],
"plugins": [{
"name": "...",
"url": "https://github.com/owner/repo",
"owner": "owner",
"repo": "repo",
"description": "...",
"category": "...",
"source": "awesome-codex-plugins",
"install_url": "https://raw.githubusercontent.com/.../plugin.json"
}]
}
```
To regenerate after editing README:
```bash
python3 scripts/generate_plugins_json.py
```