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
  • Updated guidance for PR monitoring to better cover CI checks, review feedback, and when a pull request is ready to merge.
  • Clarified how final reports should summarize addressed comments, remaining blockers, and any skipped suggestions with reasons.

[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: 19 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: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f7d972a4-c7f3-4f8c-bca3-9020db6a0045

📥 Commits

Reviewing files that changed from the base of the PR and between a3c73ef and 00ecc86.

📒 Files selected for processing (1)

• skills/pr-guardian/SKILL.md

📝 Walkthrough

Walkthrough

This PR revises skills/pr-guardian/SKILL.md, updating the "Required Behavior" checklist wording around handling actionable review comments and thread resolution, adjusting the mergeability stop condition, and simplifying the "Final Report" content requirements by removing per-thread count details.

Changes

PR Guardian Skill Documentation

Layer / File(s)	Summary
Required Behavior and stop-condition wording skills/pr-guardian/SKILL.md	Revises guidance for addressing actionable review comments, thread resolution when direct replies aren't supported, and the stop condition, now requiring no non-outdated unresolved review threads and no actionable PR comments left.
Final Report content requirements skills/pr-guardian/SKILL.md	Simplifies final report fields to emphasize review comments addressed and remaining blockers/skipped suggestions, removing explicit per-thread reply/resolution counts and unresolved thread counting.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• kaizen-agents-org/builder-agent#48: Both PRs update the same "Required Behavior" and stop-condition logic around unresolved review threads and actionable comments in SKILL.md.
• kaizen-agents-org/builder-agent#59: Both PRs refine stop-condition wording and final report requirements around unresolved review threads/comments in SKILL.md.
• kaizen-agents-org/builder-agent#66: Both PRs modify the same stopping criteria around unresolved/non-outdated review threads in SKILL.md.

🚥 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 main change: syncing Kaizen dogfood contracts into this repository.
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: a3c73ef94a

ℹ️ 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 23-26: The stop condition in SKILL.md is too strict because it
still requires zero unresolved review threads even when the fallback linked PR
comment path is used. Update the guidance around the “stop only when” rule so it
treats addressed comments as complete when a direct reply or linked PR comment
has been posted and the thread is resolved or otherwise non-blocking. Keep the
wording aligned with the “Address each actionable review comment” and “resolve
addressed review threads when repository permissions allow it” steps.

🪄 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: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0a0c9b0d-1d84-4529-80e0-85996131065a

📥 Commits

Reviewing files that changed from the base of the PR and between f57207f and a3c73ef.

📒 Files selected for processing (1)

• skills/pr-guardian/SKILL.md

[s-hiraoku]

Guardian check complete.

• Final state: CLEAN / MERGEABLE
• CI watched: GitHub Actions test passed after push 2d12384
• CodeRabbit: status success
• Fixes pushed: merged current origin/main; updated skills/pr-guardian/SKILL.md to keep outdated unresolved review threads in scope while allowing a documented non-blocking fallback when GitHub cannot resolve an addressed thread
• Review feedback addressed: replied to and resolved the Codex review thread; CodeRabbit thread was already resolved
• Local verification: npm test and npm run validate:json
• Review threads: 0 unresolved