Meta Agent v2.0 — Organisation-wide schemas and auto-detection - #1893
Meta Agent v2.0 — Organisation-wide schemas and auto-detection#1893ashleyshaw wants to merge 6 commits into
Conversation
|
Warning Review limit reached
Next review available in: 42 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚫 This PR description is missing required template content. Missing required section(s): Global DoD checklist Please update the PR body using one of the repository PR templates:
Empty placeholders, unchecked checklist boxes, and stub issue references do not count. |
github-actions
Bot
added
status:needs-review
📄 README Validation❌ One or more README checks failed.
|
Create comprehensive active project documentation for Meta Agent v2.0 implementation with clear phases, deliverables, and OpenSpec validation. ## New Files - `.github/projects/active/meta-agent-v2-2026-08-12/README.md` Project overview, problem statement, success criteria, phases - `.github/projects/active/meta-agent-v2-2026-08-12/PLANNING.md` Detailed implementation roadmap with 5 phases (Aug 12 – Sep 30+) 66 hours of effort across design, testing, deployment, real-world testing, and organisation-wide rollout - `.github/projects/active/meta-agent-v2-2026-08-12/OPENSPEC_VALIDATION.md` OpenSpec conformance validation report (95/100 score) Verifies clear specification, planning, deliverables, timeline ## Phase Overview Phase 1: Design & Schemas ✅ Complete (PR #1893) Phase 2: Validation & Testing ⏳ 3 days, 15 hours Phase 3: Deployment & Distribution ⏳ 5 days, 20 hours Phase 4: Real-World Testing ⏳ 10 days, 25 hours Phase 5: Organisation Rollout 🔵 Sep 1+, ongoing ## OpenSpec Validation Results ✅ CONFORMANT (95/100) - Problem definition: 100% - Goals & success criteria: 95% - Scope: 100% - Deliverables: 100% - Timeline: 95% - Risk management: 90% - Documentation: 100% Recommendations: - Assign Phase 2-4 owners before Aug 13 - Add contingency plans per risk - Define weekly sync meetings for Phases 3-5 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
🔍 Reviewer Summary for PR #1893CI Status: ✅ Recommendations
|
🔗 Project Linking ValidationProjects Checked: 54 ❌ Missing Related Issues SectionThe following projects are missing a "Related Issues" section in their README.md:
See Linking Standard for format. Validation Date: 2026-08-12T16:01:17.461Z |
github-actions
Bot
removed
type:documentation
Implement organisation-wide Meta agent with automatic repo-type detection and context-specific metadata standards for WordPress block plugins, themes, and control-plane files. ## Changes - **Meta Agent v2.0** (.github/agents/meta.agent.md) - Auto-detects repo type from filesystem markers - Applies context-specific frontmatter standards - Validates against repo-type schemas - Enforces UK English and consistent formatting - **Four frontmatter schemas** (schemas/) - block-plugin.frontmatter.schema.json — WordPress block plugins - block-theme.frontmatter.schema.json — WordPress block themes - control-plane.frontmatter.schema.json — .github governance files - documentation.frontmatter.schema.json — Generic documentation - **Schema documentation** (schemas/README.md) - Field reference and validation rules - Usage examples for each repo type - Integration with Meta agent - Troubleshooting guide ## Benefits ✅ Single agent works across entire organisation ✅ No manual configuration required ✅ Context-aware metadata application ✅ Consistent standards enforcement ✅ Reusable across plugin/theme repos ## Deployment Copy meta.agent.md to target repos via: 1. Single source: Reference .github repo version 2. Federated: Copy to each repo's .github/agents/ 3. Hybrid: GitHub Action for auto-sync Schemas stored in root schemas/ folder (canonical location). Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Create comprehensive active project documentation for Meta Agent v2.0 implementation with clear phases, deliverables, and OpenSpec validation. ## New Files - `.github/projects/active/meta-agent-v2-2026-08-12/README.md` Project overview, problem statement, success criteria, phases - `.github/projects/active/meta-agent-v2-2026-08-12/PLANNING.md` Detailed implementation roadmap with 5 phases (Aug 12 – Sep 30+) 66 hours of effort across design, testing, deployment, real-world testing, and organisation-wide rollout - `.github/projects/active/meta-agent-v2-2026-08-12/OPENSPEC_VALIDATION.md` OpenSpec conformance validation report (95/100 score) Verifies clear specification, planning, deliverables, timeline ## Phase Overview Phase 1: Design & Schemas ✅ Complete (PR #1893) Phase 2: Validation & Testing ⏳ 3 days, 15 hours Phase 3: Deployment & Distribution ⏳ 5 days, 20 hours Phase 4: Real-World Testing ⏳ 10 days, 25 hours Phase 5: Organisation Rollout 🔵 Sep 1+, ongoing ## OpenSpec Validation Results ✅ CONFORMANT (95/100) - Problem definition: 100% - Goals & success criteria: 95% - Scope: 100% - Deliverables: 100% - Timeline: 95% - Risk management: 90% - Documentation: 100% Recommendations: - Assign Phase 2-4 owners before Aug 13 - Add contingency plans per risk - Define weekly sync meetings for Phases 3-5 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Fix frontmatter to include file_type, category, language, owners (required fields) - Update Related Issues section with phase details and planning reference - Improve PR description with proper template (linked issues, changelog, DoD) Addresses CI validation failures: - Template enforcement (added linked issues and changelog) - Frontmatter validation (added missing required fields) - Project linking validation (improved Related Issues section)
5e4ae25 to
2f6276b
Compare
- Add language: en to PLANNING.md - Add owners to PLANNING.md - Add language: en to OPENSPEC_VALIDATION.md - Add owners to OPENSPEC_VALIDATION.md These fields are required for control-plane/project documentation.
🔗 Project Linking ValidationProjects Checked: 54 ❌ Missing Related Issues SectionThe following projects are missing a "Related Issues" section in their README.md:
See Linking Standard for format. Validation Date: 2026-08-12T16:36:42.827Z |
🔗 Project Linking ValidationProjects Checked: 54 ❌ Missing Related Issues SectionThe following projects are missing a "Related Issues" section in their README.md:
See Linking Standard for format. Validation Date: 2026-08-12T16:40:02.522Z |
🔗 Project Linking ValidationProjects Checked: 54 ❌ Missing Related Issues SectionThe following projects are missing a "Related Issues" section in their README.md:
See Linking Standard for format. Validation Date: 2026-08-12T16:44:06.823Z |
Resolves project linking validation error by adding Related Issues section with phase tracking table as per LINKING_STANDARD.md
- Changed file_type from 'project' to 'project-readme' - Added owners field for control-plane governance
❌ Branch Name Validation FailedThe branch name Required Format
Allowed Branch Types
Valid Examples
Invalid Examples
SolutionRename your branch to follow the pattern and update the PR. For more information, see docs/BRANCHING_STRATEGY.md. |
🔗 Project Linking ValidationProjects Checked: 54 ✅ All projects have Related Issues sectionsDetailed issue link validation is deferred to Phase 4. Validation Date: 2026-08-12T22:07:48.418Z |
There was a problem hiding this comment.
Pull request overview
This PR introduces Meta Agent v2.0 documentation and new repo-type-specific frontmatter JSON Schemas intended to standardise Markdown metadata across LightSpeedWP repos, alongside project planning artefacts for the rollout.
Changes:
- Added four new JSON Schemas for validating Markdown frontmatter by repo type (block plugin, block theme, control-plane, generic docs).
- Expanded
schemas/README.mdinto a detailed schema reference and usage guide. - Added project planning documents for the Meta Agent v2.0 initiative and updated related project docs.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
schemas/README.md |
Replaces the previous short README with a comprehensive schema reference and usage guidance. |
schemas/block-plugin.frontmatter.schema.json |
Adds a new frontmatter schema intended for block plugin documentation. |
schemas/block-theme.frontmatter.schema.json |
Adds a new frontmatter schema intended for block theme documentation. |
schemas/control-plane.frontmatter.schema.json |
Adds a new frontmatter schema intended for .github / control-plane governance documentation. |
schemas/documentation.frontmatter.schema.json |
Adds a new frontmatter schema intended for general documentation. |
.github/agents/meta.agent.md |
Updates Meta Agent documentation/spec to describe repo-type auto-detection and schema-driven validation. |
.github/projects/active/reviewer-agent-v2-2026-08/README.md |
Adds a “Related Issues” section to the Reviewer Agent v2 project README. |
.github/projects/active/meta-agent-v2-2026-08-12/README.md |
Adds a new project README describing Meta Agent v2.0 scope, phases, and references. |
.github/projects/active/meta-agent-v2-2026-08-12/PLANNING.md |
Adds a detailed multi-phase roadmap and task breakdown for Meta Agent v2.0. |
.github/projects/active/meta-agent-v2-2026-08-12/OPENSPEC_VALIDATION.md |
Adds an OpenSpec conformance report for the Meta Agent v2.0 project documentation. |
Suppressed comments (1)
.github/projects/active/meta-agent-v2-2026-08-12/README.md:373
- These relative links point to non-existent paths from within
.github/projects/active/meta-agent-v2-2026-08-12/. They should use correct relative paths to repo-root files so link checking and navigation work.
- [Meta Agent v2.0](./.github/agents/meta.agent.md) — Full agent documentation
- [Schema Reference](./schemas/README.md) — Field reference and validation rules
- [CLAUDE.md](./CLAUDE.md) — Organisation-wide standards
- [PR #1893](https://github.com/lightspeedwp/.github/pull/1893) — Implementation PR
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| --- | ||
| file_type: "documentation" | ||
| title: "Portable Schemas" | ||
| description: "Ownership index for portable schemas used by LightSpeed AI assets and plugin metadata." | ||
| version: 'v0.1.2' | ||
| last_updated: '2026-06-01' | ||
| maintainer: LightSpeed Team | ||
| authors: | ||
| - Codex | ||
| license: GPL-3.0 | ||
| tags: | ||
| - schemas | ||
| - ai-ops | ||
| - plugin-restructure | ||
| domain: governance | ||
| stability: stable | ||
| --- | ||
|
|
||
| *Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP* | ||
| [Contact](https://lightspeedwp.agency/contact) | ||
|
|
||
| *Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP* | ||
| [Contact](https://lightspeedwp.agency/contact) | ||
|
|
||
| *Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP* | ||
| [Contact](https://lightspeedwp.agency/contact) | ||
| title: Frontmatter Schemas | ||
| description: JSON Schema definitions for validating Markdown frontmatter metadata across LightSpeedWP repos | ||
| file_type: reference | ||
| category: standards | ||
| status: active | ||
| language: en | ||
| version: 1.0.0 | ||
| author: LightSpeed | ||
| maintainer: Ash Shaw | ||
| --- |
| | `version` | string | ❌ | Semantic version or v1.2 format | | ||
| | `references` | object | ❌ | Links to related resources | | ||
|
|
| "prerequisites": { | ||
| "type": "array", | ||
| "description": "Prerequisites for following this document", | ||
| "items": { | ||
| "type": "string" | ||
| } | ||
| }, | ||
| "references": { | ||
| "type": "object", | ||
| "description": "Links to related resources", | ||
| "additionalProperties": { | ||
| "type": "string", | ||
| "format": "uri" | ||
| } | ||
| }, | ||
| "table_of_contents": { | ||
| "type": "boolean", | ||
| "description": "Whether this document needs a table of contents" | ||
| }, | ||
| "version": { | ||
| "type": "string", | ||
| "pattern": "^\\d+\\.\\d+(\\.\\d+)?$", | ||
| "description": "Document version number" | ||
| }, |
| "references": { | ||
| "type": "object", | ||
| "description": "Links to related resources", | ||
| "additionalProperties": { | ||
| "type": "string", | ||
| "format": "uri" | ||
| } | ||
| }, | ||
| "file_type": { | ||
| "type": "string", | ||
| "enum": ["documentation", "guide", "reference"], | ||
| "description": "Type of file" | ||
| }, |
| "references": { | ||
| "type": "object", | ||
| "description": "Links to related resources", | ||
| "additionalProperties": { | ||
| "type": "string", | ||
| "format": "uri" | ||
| } | ||
| }, | ||
| "file_type": { | ||
| "type": "string", | ||
| "enum": ["documentation", "guide", "reference", "pattern"], | ||
| "description": "Type of file" | ||
| }, |
| "references": { | ||
| "type": "object", | ||
| "description": "Links to related resources", | ||
| "additionalProperties": { | ||
| "type": "string", | ||
| "format": "uri" | ||
| } | ||
| }, | ||
| "last_reviewed": { | ||
| "type": "string", | ||
| "format": "date", | ||
| "description": "Date of last content review in YYYY-MM-DD format" | ||
| }, |
| owners: | ||
| - lightspeedwp/maintainers | ||
| owners: | ||
| - lightspeedwp/maintainers |
| | TBD | epic | Phase 4: Documentation & Rollout | 🔵 Planned | | ||
| | TBD | epic | Phase 5: Monitoring & Iteration | 🔵 Future | | ||
|
|
||
| **Note:** GitHub issues will be created as phases progress. See [[OPENSPEC_PLAN.md](./OPENSPEC_PLAN.md)] for detailed task breakdown. |
|
|
||
| For each Markdown file, the agent: | ||
|
|
||
| 1. **Validates** existing frontmatter against `schemas/{repo-type}.frontmatter.schema.json` |
| # Validate a single file against block-plugin schema | ||
| npx ajv validate -s schemas/block-plugin.frontmatter.schema.json docs/guide.md | ||
|
|
||
| # Validate all docs in a block plugin | ||
| npx ajv validate -s schemas/block-plugin.frontmatter.schema.json docs/**/*.md |
Summary
Implement organisation-wide Meta Agent v2.0 with automatic repo-type detection and context-specific metadata standards. Single agent works across WordPress block plugins, themes, and control-plane repos.
Linked Issues
Relates to:
Changes
Meta Agent v2.0 — Auto-detects repo type (block plugin, block theme, control-plane, generic)
Four frontmatter schemas — JSON Schema Draft 2020-12 validation
block-plugin.frontmatter.schema.json— WordPress block pluginsblock-theme.frontmatter.schema.json— WordPress block themescontrol-plane.frontmatter.schema.json— .github governance filesdocumentation.frontmatter.schema.json— Generic documentationComprehensive documentation
Active project with clear planning
Test Plan
Global DoD Checklist
Changelog
Added
Changed
🤖 Generated with Claude Code