docs: complete Wave 5 child audits #654 #655 #656#792
Conversation
Add issue-template inventory, template-to-automation mapping, and labeler issue-rules audits for Wave 5 child issues. Closes #654 Closes #655 Closes #656 https://claude.ai/code/session_f7cb7a8b-a13f-4467-b626-c66953488ccd
|
Warning Review limit reached
More reviews will be available in 42 minutes and 45 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 selected for processing (3)
✨ 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 |
github-actions
Bot
added
status:needs-review
🔍 Reviewer Summary for PR #792CI Status: ✅ Recommendations
|
github-actions
Bot
added
type:chore
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces three comprehensive audit reports detailing issue labeling rules, template-to-automation trigger mappings, and issue template standardization. The feedback focuses on correcting minor spelling inconsistencies to align with the repository's American English conventions, specifically updating terms like 'labelling', 'standardised', and 'favours'.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| ## Executive Summary | ||
|
|
||
| `.github/labeler.yml` is currently structured around PR-friendly signals (`head-branch`, `changed-files`) and has limited native issue-specific rule expression. Issue labelling exists in practice through the unified labeling workflow and agent heuristics rather than through rich issue-specific config rules. |
There was a problem hiding this comment.
To maintain consistency with the American English spelling convention used throughout the repository (e.g., labeling.yml, labeling.agent.js, and standardization), please use "labeling" instead of "labelling".
| `.github/labeler.yml` is currently structured around PR-friendly signals (`head-branch`, `changed-files`) and has limited native issue-specific rule expression. Issue labelling exists in practice through the unified labeling workflow and agent heuristics rather than through rich issue-specific config rules. | |
| .github/labeler.yml is currently structured around PR-friendly signals (head-branch, changed-files) and has limited native issue-specific rule expression. Issue labeling exists in practice through the unified labeling workflow and agent heuristics rather than through rich issue-specific config rules. |
| ## Findings | ||
|
|
||
| 1. `labeler.yml` has broad PR coverage and narrow issue-native coverage. | ||
| 2. Issue labelling works, but largely through procedural logic in `labeling.agent.js`. |
There was a problem hiding this comment.
To maintain consistency with the American English spelling convention used throughout the repository, please use "labeling" instead of "labelling".
| 2. Issue labelling works, but largely through procedural logic in `labeling.agent.js`. | |
| 2. Issue labeling works, but largely through procedural logic in labeling.agent.js. |
|
|
||
| ## Executive Summary | ||
|
|
||
| Issue templates are structurally standardised, but they do not currently provide deterministic label/type triggers in frontmatter. Automation is therefore primarily workflow-driven and heuristic-driven after issue creation. |
There was a problem hiding this comment.
To maintain consistency with the American English spelling convention used throughout the repository (e.g., standardization in the other audit reports), please use "standardized" instead of "standardised".
| Issue templates are structurally standardised, but they do not currently provide deterministic label/type triggers in frontmatter. Automation is therefore primarily workflow-driven and heuristic-driven after issue creation. | |
| Issue templates are structurally standardized, but they do not currently provide deterministic label/type triggers in frontmatter. Automation is therefore primarily workflow-driven and heuristic-driven after issue creation. |
| - `head-branch` mappings drive many `type:*`, `status:*`, and `priority:*` outcomes. | ||
| - `changed-files` mappings drive `area:*` and `lang:*` labels. | ||
|
|
||
| Issue context has no branch or changed-files signals, so the current `.github/labeler.yml` rule design naturally favours PR events. |
There was a problem hiding this comment.
To maintain consistency with the American English spelling convention used throughout the repository, please use "favors" instead of "favours".
| Issue context has no branch or changed-files signals, so the current `.github/labeler.yml` rule design naturally favours PR events. | |
| Issue context has no branch or changed-files signals, so the current .github/labeler.yml rule design naturally favors PR events. |
| ## Findings | ||
|
|
||
| 1. Numbering and baseline standardization are good (26 sequential templates). | ||
| 2. Direct template-driven labelling is not configured in issue templates (`labels` absent in all numbered templates). |
There was a problem hiding this comment.
To maintain consistency with the American English spelling convention used throughout the repository, please use "labeling" instead of "labelling".
| 2. Direct template-driven labelling is not configured in issue templates (`labels` absent in all numbered templates). | |
| 2. Direct template-driven labeling is not configured in issue templates (labels absent in all numbered templates). |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3cffc53ca
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| | Template Set | Expected Automation | Current Status | Missing Pieces | | ||
| |---|---|---|---| | ||
| | Numbered issue templates (`01`-`26`) | Deterministic `type:*` and baseline triage labels on create | Partial (agent infers from text) | No template `labels`, no deterministic per-template mapping in config | |
There was a problem hiding this comment.
For template-created issues without an existing type:* label, the inspected runtime path does not reliably infer the template type from text: scripts/agents/includes/status-enforcer.js applies default type:task before content detection, and scripts/agents/labeling.agent.js only has keywords for a subset of types, omitting several numbered templates such as epic, story, design, audit, help/support, release, and AI Ops. Marking the current status as “agent infers from text” can close #655 while missing the main automation gap: many templates still become generic tasks or duplicate type labels rather than deterministic template-specific types.
Useful? React with 👍 / 👎.
1 participant
Summary\n- add audit report for #654 template inventory and standardization\n- add audit report for #655 issue-template to automation trigger mapping\n- add audit report for #656 issue-labeling rules in labeler.yml\n- close #654, #655, and #656 with completion comments\n\n## Validation\n- npm run lint:md\n\n## Reports\n- .github/reports/audits/2026-06-03-issue-template-inventory-standardization-audit-654.md\n- .github/reports/audits/2026-06-03-issue-template-automation-trigger-mapping-audit-655.md\n- .github/reports/audits/2026-06-03-issue-labeling-rules-in-labeler-audit-656.md