You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-suppress maintainer-owned queue noise unless it is the best fix path
91
+
-exclude PRs authored by wide-access maintainers until `created_at`is at least 14 days old; only a named PR or explicit maintainer-work request overrides
92
92
- identify opener/author and preserve credit
93
93
- decide: `repair-existing-pr`, `create-new-pr`, `close-fixed-on-main`, `close-duplicate`, or `reject`
Copy file name to clipboardExpand all lines: .agents/skills/openclaw-pr-maintainer/SKILL.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,9 +76,9 @@ gh api -X POST "repos/openclaw/openclaw/issues/<number>/assignees" -f 'assignees
76
76
- If `name` is empty, use the login only. If profile lookup is rate-limited or unavailable, say `account age unknown` rather than omitting the opener.
77
77
- Use identity and activity as triage signal, not proof by itself: new, low-activity, or bot-like accounts can raise review caution, but code, repro, and CI evidence still decide.
78
78
79
-
## Suppress top-maintainer items in issue triage
79
+
## Suppress recent wide-access maintainer PRs in triage
80
80
81
-
When asked for issue triage, hot issues, pressing bugs, Discord-correlated issues, or "what is still open", do not surface issues or PRs authored by top maintainers by default. Prefer external/user-reported hot issues and external PRs, not maintainer-owned work queues.
81
+
In generic issue/PR triage, hot queues, landable shortlists, or "what is still open", exclude PRs authored by maintainers with broad repository access until 14 days after `created_at`. Prefer external contributors' PRs. An ordinary request for landing candidates does not override the age gate. Continue suppressing maintainer-authored issues by default.
82
82
83
83
Suppress by default when the opener/author is one of:
84
84
@@ -107,8 +107,9 @@ Also suppress lower-priority maintainer-owned noise from the broader keep/top-ma
107
107
108
108
Exceptions:
109
109
110
-
- Show maintainer-authored items when the requester explicitly asks for maintainer PRs/issues, PR landing candidates, release-blocking maintainer work, or a specific PR/issue number.
111
-
- Show a maintainer-authored item when it is the canonical fix for an external hot issue, but frame it as the fix path rather than as a user-facing issue candidate.
110
+
- Once a maintainer-authored PR is at least 14 days old, triage it normally.
111
+
- A specific PR/issue number or an explicit request for maintainer-owned work overrides suppression.
112
+
- When a recent maintainer PR is the canonical fix for an external hot issue, mention it only as the fix path; do not count it as a triage or landing candidate.
112
113
- Do not close, label, or deprioritize solely because an item is maintainer-authored; this section only controls what appears in triage shortlists.
Copy file name to clipboardExpand all lines: AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,6 +159,7 @@ Skills own workflows; root owns hard policy and routing.
159
159
- PR superseded by `main`: if code proof shows `main` already has same-or-better behavior, comment canonical commit/PR + focused proof, then close. Bar high: inspect PR diff, current code/tests, linked issue, caller/sibling path. If unsure, leave open.
160
160
- Issue/PR numbers need a short summary every time; assume the reader has not opened or read them.
161
161
- Before presenting a batch of issues/PRs, use smart subagents to verify live state and current `main`; omit closed/fixed items, and comment+close items already fixed on `main` when maintainer action is authorized.
162
+
- Generic triage and landing shortlists: exclude PRs authored by maintainers with broad repository access until 14 days after creation. An ordinary request for landing candidates does not override this gate; only a named PR or explicit request for maintainer-owned work does.
162
163
- PR review answer: bug/behavior, URL(s), affected surface, provenance for regressions when traceable, best-fix judgment, evidence from code/tests/CI/current or shipped behavior.
163
164
- PR reviewable findings: post them on the PR, not chat-only, so author sees actionable feedback.
164
165
- Issue/PR final answer: last line is the full GitHub URL.
0 commit comments