Skip to content

docs: Issue status review — DoR/DoD completion audit - #2263

Closed
ashleyshaw wants to merge 2 commits into
developfrom
docs/dor-dod-audit
Closed

docs: Issue status review — DoR/DoD completion audit#2263
ashleyshaw wants to merge 2 commits into
developfrom
docs/dor-dod-audit

Conversation

@ashleyshaw

Copy link
Copy Markdown
Member

Linked issues

Closes#1930, #2051
Relates to #2186, #2147, #2049

What changed

Audience & placement

  • Audience: Contributors, issue maintainers, project managers
  • Location:.github/ (control-plane documentation)

Notes

Changelog

Added


Checklist (Global DoD / PR)

  • All AC met and demonstrated
  • Tests added/updated (not applicable — documentation/issue audit only)
  • Accessibility checklist completed (not applicable — documentation):
    • N/A — documentation only
  • Docs/readme/changelog updated (CHANGELOG.md entry added; audit document created)
  • Security checklist completed (not applicable — documentation only):
    • N/A — documentation only
  • Code/design reviews — ready for review
  • CI green; linked issues closed; release notes prepared (pending CI completion)

Generated by Claude Code

- Closed#1930: PR template validator false negative (merged via #2007, #2010)
- Closed#2051: Frontmatter freshness CI issues (merged via #2180)
- Updated #2186: Template validation script false positives with DoR/DoD
- Updated #2147: Phase 1 validation tests progress tracking with DoR/DoD framework
- Verified #2049: OpenSpec Labels Phase 2-3 epic (complete, merged)
All high-priority issues now have complete Definition of Ready and Definition of Done sections reflecting merged work into develop branch.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018MoY39EXD6tnbbjs3JVUqT
- Add comprehensive CHANGELOG entry for DoR/DoD audit
- Update branch reference from old branch to docs/dor-dod-audit
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018MoY39EXD6tnbbjs3JVUqT
@coderabbitai

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in:54 minutes

Limit details: You’ve used the included review currently available.

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?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 5c78dadb-5dab-4500-9bd0-b41a12f84ba7

📥 Commits

Reviewing files that changed from the base of the PR and between 5c62094 and 342fc9f.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • ISSUE_STATUS_REVIEW_2026-08-21.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

🚫 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

Copy link
Copy Markdown
Contributor

❌ Branch Name Validation Failed

The branch name docs/dor-dod-audit does not follow the LightSpeed branching strategy.

Required Format

{type}/{scope}-{short-title}
  • type: one of the allowed prefixes (lowercase)
  • scope: lowercase, hyphens only (no underscores or uppercase)
  • title: lowercase, hyphens only (no underscores or uppercase)

Allowed Branch Types

feat, fix, hotfix, release, refactor, chore, docs, test, perf, ci, build, deps, security, revert, research, design, a11y, ux, i18n, ops, proto, ds, api, schema, telemetry, content, seo, config, migrate, qa, uat, audit, codex

Valid Examples

  • feat/branch-naming-enforcement
  • fix/validation-script-bug
  • chore/update-dependencies
  • docs/branching-strategy-guide
  • hotfix/critical-security-patch

Invalid Examples

  • claude/my-branch (type "claude" not allowed)
  • Feature/MyBranch (uppercase not allowed)
  • fix-bug (missing type prefix)
  • feat/my_feature (underscores not allowed)
  • feat/MyFeature (uppercase not allowed)

Solution

Rename your branch to follow the pattern and update the PR.

For more information, see docs/BRANCHING_STRATEGY.md.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

investigate: PR template validator false negative on 'Changelog' and 'Global DoD Checklist' sections

2 participants

@ashleyshaw@claude