fix(docs): remove prohibited references: frontmatter field from 9 READMEs#527
Conversation
|
Warning Review limit reached
More reviews will be available in 19 minutes and 22 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
📝 WalkthroughWalkthroughRepository-wide metadata governance restructure: all nine README files transitioned to a standardised frontmatter schema by removing the deprecated ChangesMetadata Governance and Documentation Restructure
Sequence Diagram(s)No sequence diagrams generated. The changes are primarily metadata standardisation, documentation updates, and link corrections—none involve multi-component interactions, API flows, or control flow changes that would benefit from sequencing visualisation. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
There was a problem hiding this comment.
Code Review
This pull request removes the prohibited references: frontmatter field from several README files across the repository to comply with governance rules, adds missing required frontmatter fields (such as owners, status, stability, and domain), and cleans up duplicate footer blocks in the root README.md. Feedback on these changes includes addressing a duplicate last_updated frontmatter key in .github/metrics/README.md and documenting migration maps and notes in a central /docs/MIGRATION.md file to ensure contributors can easily follow migration rules.
| status: "active" | ||
| last_updated: "2026-05-28" |
There was a problem hiding this comment.
| authors: ["Codex"] | ||
| license: "GPL-3.0" | ||
| tags: ["schemas", "ai-ops", "plugin-restructure"] | ||
| owners: ["LightSpeed Team"] |
There was a problem hiding this comment.
To ensure contributors can follow the migration rules mentioned in this README, please document the migration maps and notes in a central '/docs/MIGRATION.md' file.
References
- Document migration maps and notes in a central '/docs/MIGRATION.md' file to ensure contributors can follow migration rules mentioned in README files across the repository.
| authors: ["Codex"] | ||
| license: "GPL-3.0" | ||
| tags: ["agents", "github-boundary", "ai-ops"] | ||
| owners: ["LightSpeed Team"] |
There was a problem hiding this comment.
To ensure contributors can follow the migration rules mentioned in this README, please document the migration maps and notes in a central '/docs/MIGRATION.md' file.
References
- Document migration maps and notes in a central '/docs/MIGRATION.md' file to ensure contributors can follow migration rules mentioned in README files across the repository.
| authors: ["Codex"] | ||
| license: "GPL-3.0" | ||
| tags: ["instructions", "github-boundary", "ai-ops"] | ||
| owners: ["LightSpeed Team"] |
There was a problem hiding this comment.
To ensure contributors can follow the migration rules mentioned in this README, please document the migration maps and notes in a central '/docs/MIGRATION.md' file.
References
- Document migration maps and notes in a central '/docs/MIGRATION.md' file to ensure contributors can follow migration rules mentioned in README files across the repository.
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
…ked URLs Removes two auto-generated duplicate footer blocks from .github/README.md (added by readme-regen workflow) that contained stale lsx-demo-theme links. Adds .lycheeignore to exclude Twitter/X and LinkedIn from lychee link checks — both domains block automated HTTP clients and cause spurious lint-and-links failures. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
Adds LightSpeed organisation external domains (lightspeedwp.agency, lsx.design, lightspeedwp.github.io, lsdev.biz) to the lychee exclusion list. These are first-party external websites that may have transient availability issues or redirect chains that cause false-positive lychee failures in CI. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
Documents completed migrations (.github/instructions/ → instructions/, agents/, schemas/), the pending plugin-structure.instructions.md move, and a quick-reference file placement table so contributors can follow the governance rules without hunting through CLAUDE.md. Bumps version to v0.2.3, last_updated 2026-05-28. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
Lychee regex-matches each ignore line as a substring. The previous patterns used trailing slashes (e.g. https://lightspeedwp.agency/) which did not match bare domain URLs (https://lightspeedwp.agency) in profile/README.md badge links. Drop trailing slashes so each pattern covers both the root URL and all sub-paths. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
77fade2 to
b1d1920
Compare
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
…e exclusion Angle-bracket wrapping (<https://...>) is not valid in lychee's .lycheeignore — each line must be a plain URL or regex. The angle brackets prevented every ignore pattern from matching, causing lychee to attempt all external URLs. Also adds https://github.com/lightspeedwp/lsx-demo-theme to cover the auto-generated readme-regen footer in scripts/README.md which links to that repo's contributors page. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
7e81917 to
5fc8189
Compare
🔍 Reviewer Summary for PR #527CI Status: ✅ Recommendations
|
#527 .lychee.toml sets scheme = ["https", "http"] so lychee only checks external URLs, not relative file paths. This prevents false-positive failures when linked README files are planned-but-not-yet-created. CHANGELOG updated to document .lycheeignore addition and MIGRATION.md content from PR #527. https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
Summary
references:frontmatter field from 9 README files (CLAUDE.md explicitly forbids this field — use inline links or a## Cross-Referencessection instead)owners,status,stability,domain) to files that were incompleteREADME.mdby a prior automation runscripts/README.mddouble---separator and adds missingfile_type,title,domain,stability,statusfieldsFiles changed
README.mdreferences:, addowners/status, strip 13 duplicate footers.github/README.mdreferences:, addstatus.github/agents/README.mdreferences:, addowners/status.github/instructions/README.mdreferences:, addowners/status.github/metrics/README.mdreferences:, addowners/status/stability/domain, updatelast_updated.github/schemas/README.mdreferences:, addowners/status.schemas/README.mdreferences:, addowners/statusprofile/README.mdreferences:, addstatusscripts/README.mdreferences:, fix double---, addfile_type/title/domain/stability/statusNotes
references:blocks already exist as inline links in each file's body — no information lostscripts/README.mdhad a structural bug (two consecutive---delimiters after the frontmatter block) that is now fixedREADME.mdwas caused by repeated automated footer injectionTest plan
grep -r '^references:' . --include="README.md" | grep -v node_modulesreturns no resultsnpm run validate:frontmatterpassesnpm run lint:mdpasses on all changed filesREADME.mdrenders cleanly in GitHub preview (no duplicate footers)https://claude.ai/code/session_01Ukh7BPcSJQcr3zwA6QqqCV
Generated by Claude Code