Sync Kaizen dogfood contracts

[s-hiraoku]

Summary

• Sync deterministic Kaizen dogfood contracts from kaizen-agents-org/.github.
• Update only the manifest-managed shared skills, issue template, Kaizen config, and agent guidance.

Verification

• Automated sync copied and compared every manifest-managed path.

Generated by the daily dogfood sync workflow.
Source issue: not supplied by this automated sync run.

Summary by CodeRabbit

• Documentation
  • Simplified the PR Guardian status report so it focuses on the most important review outcomes: merge readiness, completed feedback, and any remaining blockers.
  • Streamlined the review checklist to emphasize addressing comments and explaining any unresolved or skipped items.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e924a73f-5817-4b13-b383-d491e509227e

📥 Commits

Reviewing files that changed from the base of the PR and between 5b0bfd8 and 44f732a.

📒 Files selected for processing (1)

• skills/pr-guardian/SKILL.md

📝 Walkthrough

Walkthrough

The PR Guardian skill's PR-state gathering step was narrowed to a smaller set of gh pr view JSON fields plus gh pr checks, removing prior mergeability/review-comment aggregates and a GraphQL review-thread query. The Final Report checklist and template were simplified, dropping per-thread reply/resolution counts in favor of mergeability, runs, commits, and remaining blockers.

Changes

PR Guardian SKILL.md updates

Layer / File(s)	Summary
Simplified PR state fetch and final report checklist skills/pr-guardian/SKILL.md	Narrowed gh pr view JSON fields (url, state, isDraft, mergeStateStatus, baseRefName, headRefName, statusCheckRollup, reviewDecision) plus gh pr checks, removing GraphQL review-thread queries; simplified Final Report to focus on mergeability, watched runs/commits, feedback addressed, and remaining blockers instead of per-thread counts.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• kaizen-agents-org/kaizen-loop#16: Initially adds the same skills/pr-guardian/SKILL.md that this PR updates the Required Behavior/Final Report logic for.
• kaizen-agents-org/kaizen-loop#57: Updates the same Required Behavior/final reporting logic for ensuring unresolved items include reasons.
• kaizen-agents-org/coderabbit#23: Updates the same skills/pr-guardian/SKILL.md Required Behavior/stop-condition logic and review-comment checklist semantics.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the PR’s main intent: syncing Kaizen dogfood contracts and related shared guidance updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/daily-dogfood-sync

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9ad00299a

ℹ️ 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".

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@skills/pr-guardian/SKILL.md`:
- Around line 16-23: Step 2 no longer gathers enough review-thread data to
satisfy step 8’s requirement to stop only when there are no unresolved or
outdated threads. Update the SKILL.md guidance around the PR inspection flow so
the data collection and stop condition match: either restore a minimal thread
lookup using the PR review-thread source already implied by the workflow, or
revise step 8 to remove the unresolved-thread wording and rely only on the
fields returned by gh pr view and gh pr checks. Keep the instructions in sync
with the existing PR-checking steps and the thread-resolution validation
requirement.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3966e6d9-845f-476d-956a-1b73b523b27e

📥 Commits

Reviewing files that changed from the base of the PR and between c091d11 and 5b0bfd8.

📒 Files selected for processing (1)

• skills/pr-guardian/SKILL.md

[s-hiraoku]

PR guardian status:

• Mergeability: CLEAN / MERGEABLE.
• Checks watched: validate and CodeRabbit passed after commits 5b0bfd8 and 44f732a.
• Fixes pushed: counted outdated unresolved review threads as blockers again, and restored the GraphQL reviewThreads lookup needed to verify that stop condition.
• Review feedback addressed: Codex thread and follow-up CodeRabbit thread replied to and resolved.
• Current unresolved review threads: 0.
• Remaining blockers: none observed.