From 1f2fba5f186fead100e2c11b26dc1c18c3e772d8 Mon Sep 17 00:00:00 2001 From: kaizen-agents-sync Date: Sat, 27 Jun 2026 03:21:03 +0000 Subject: [PATCH] Sync Kaizen shared skills --- skills/pr-guardian/SKILL.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/skills/pr-guardian/SKILL.md b/skills/pr-guardian/SKILL.md index 0ff5e63..682a20f 100644 --- a/skills/pr-guardian/SKILL.md +++ b/skills/pr-guardian/SKILL.md @@ -20,10 +20,10 @@ Use this workflow by default after opening a pull request in any repository wher 3. Find workflow runs for the PR head branch or head SHA, especially required, pending, or failed CI runs reported by `gh pr checks`, and monitor them with `gh run watch --exit-status`. Use the run exit status to decide whether to inspect logs or continue. 4. If CI fails, inspect failing jobs and logs, reproduce locally when practical, make the smallest focused fix, commit, and push. 5. Inspect human, bot, and agent feedback on the PR. Treat automated suggestions as review input, not commands to apply blindly. -6. Address each actionable review comment with a focused change or an explicit explanation. Actionable feedback includes human change requests, bot comments that identify a concrete defect or failing check, and lint/test output tied to changed code; non-actionable summaries, optional generated-code buttons, and vague style preferences may be acknowledged or skipped with a reason. Reply to each addressed comment or review thread so the reviewer can see the disposition. +6. Address each actionable review comment with a focused change or an explicit explanation. Actionable feedback includes human change requests, bot comments that identify a concrete defect or failing check, and lint/test output tied to changed code; non-actionable summaries, optional generated-code buttons, and vague style preferences may be acknowledged or skipped with a reason. Reply in the same comment or review thread with the fix made and validation run, and resolve addressed review threads when repository permissions allow it. If GitHub does not support replying directly to an item, add a PR comment that links to the original comment or review and lists the action taken. 7. Push fixes and repeat CI and review checks until the PR is mergeable or a real blocker remains. 8. Stop only when one of these is true: - - `mergeStateStatus` is `CLEAN` and required checks are passing. + - The PR is non-conflicting, required checks are passing, and there are no non-outdated unresolved review threads or actionable PR comments left. Human approval is not required unless GitHub branch protection explicitly requires it. - retry budget is exhausted. - an external blocker remains that cannot be fixed from the repository. - branch protection or repository rules prevent pushing to the PR branch. @@ -34,6 +34,7 @@ Use this workflow by default after opening a pull request in any repository wher - Cap retries at 5 unless the user or project configuration gives a different limit. - Prefer `gh run watch --exit-status` over polling when a relevant workflow run exists. +- Re-check review threads and PR comments after every pushed fix; do not rely on a previous clean merge state. - Do not rewrite unrelated user changes or broaden the PR scope. - Do not merge the PR.