feat: Reporting Agent v2 — multi-repository support with automatic context detection - #2498
Conversation
📄 README Validation❌ One or more README checks failed.
|
🎨 Mermaid Diagram Validation❌ One or more Mermaid diagram checks failed.
|
🔍 Reviewer Summary for PR #2498CI Status: ❌ Recommendations
|
1 similar comment
🔍 Reviewer Summary for PR #2498CI Status: ❌ Recommendations
|
|
Missing required section(s): Linked issues, Changelog, Global DoD checklist This is a post-merge backstop for admin bypasses. Please review branch protection for develop. |
🔍 Reviewer Summary for PR #2498CI Status: ❌ Recommendations
|
|
This PR's branch name Standard pattern: Based on linked issue type: Correct template should be: No action required — this is informational. Future PRs should use the correct branch name. See Branching Strategy for more info. |
…y-aware templates - Add RepoContextDetector class: detects block-plugin, block-theme, control-plane, platform, and unknown repo types from file signals and GitHub topic metadata - Add repo-templates.js: five repository-aware Markdown report templates with typed domain sections and required frontmatter - Add unit tests for both modules (context detector + templates) - Update .github/agents/reporting.agent.md to v2.0 with multi-repo support, context detection docs, and repository type table - Add SPECIFICATION.md: OpenSpec architecture specification with detection signal tables, template spec, and acceptance criteria - Add PLANNING.md: phase planning with deliverables and timeline - Update project README.md to reflect v2 completion status Closes #1898 Co-authored-by: ashleyshaw <1805352+ashleyshaw@users.noreply.github.com>
- Fix RepoContextDetector._isControlPlane() to use prefix-based matching (.some() with startsWith()) so nested file paths like '.github/workflows/ci.yml' and 'agents/foo.js' are correctly detected (was using Set.has() which only matched exact bare names) - Update corresponding test to cover nested-path detection case - Replace non-approved Mermaid classDef fill colours in SPECIFICATION.md with org-approved WCAG 2.2 AA palette from mermaid.instructions.md Co-authored-by: ashleyshaw <1805352+ashleyshaw@users.noreply.github.com>
5180ef4 to
5085bfa
Compare
❌ 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. |
Agent Spec Validation❌ Agent spec validation failed
See the workflow run for detailed validation results. |
Agent Spec Validation❌ Agent spec validation failed
See the workflow run for detailed validation results. |
🔍 Reviewer Summary for PR #2498CI Status: ❌ Recommendations
|
Agent Spec Validation❌ Agent spec validation failed
See the workflow run for detailed validation results. |
Summary
Upgrades Reporting Agent to v2.0 with zero-config repository type detection and context-aware report templates, replacing single-template approach with five typed scaffolds for the full LightSpeed repository landscape.
Changes Made
Added
Context detection (
agents/metadata-agent/lib/context/repo-context-detector.js)RepoContextDetectorclass for automatic repo type detection.php+block.json,theme.json,DockerfilefilesRepository-aware templates (
agents/metadata-agent/lib/templates/repo-templates.js)block-plugin— Plugin Health, Block Inventory, Security & Complianceblock-theme— Theme Health, Design System, Accessibility Checkscontrol-plane— Agent & Automation Health, Workflow Activity, Metricsplatform— Infrastructure Health, Deployment Activityunknown— Generic fallbackAgent prompt spec (
/.github/agents/reporting.agent.md)Project documentation
SPECIFICATION.md— OpenSpec architecture with component diagramPLANNING.md— Phase planning with deliverables and success criteriaUnit tests — Full coverage of context detector and all templates
Linked Issue
Resolves #1898
🤖 Generated with Claude Code