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
Copy file name to clipboardExpand all lines: skills/maintainer-orchestrator/SKILL.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,13 @@ Repeat synchronization after every landing and before any release gate.
51
51
52
52
Do not treat ordinary draft, stale, difficult, or platform-specific items as ignored. Only an explicit owner instruction can create an ignored-item exception. Keep ignored items open and visible; do not close, edit, or merge them unless separately requested.
53
53
54
+
## Immediate Noise Closeout
55
+
56
+
- Close an issue immediately and silently as not planned/spam when its content is clearly spam, incoherent or nonsensical, unrelated outreach, recruiting, sales, promotion, a scam, or contains no coherent repository request. Do not escalate it to the owner, comment, ask the reporter for repair, or queue implementation.
57
+
- Language alone is never a spam signal. Translate and understand foreign-language reports before classifying their content.
58
+
- Keep potentially legitimate, security-sensitive, or materially ambiguous reports in normal triage.
59
+
- This standing authority is the only routine exception to per-item close authorization. It authorizes the issue close only, not code, branch, PR, comment, or release mutations.
60
+
54
61
## Control-Plane Ownership
55
62
56
63
- Only this root orchestrator session may create, reuse, fork, assign, rename, archive, or steer worker threads.
@@ -167,6 +174,7 @@ Treat triage, monitoring, implementation, public mutation, and release as separa
167
174
- Push permission does not imply merge or close permission.
168
175
- CI rerun and CI-fix permission must be explicit; a push alone does not authorize additional repair commits or workflow mutations.
169
176
- Merge/close permission must be explicit for the affected work.
177
+
- Clearly qualifying noise under `Immediate Noise Closeout` has standing silent-close authority and does not require per-item escalation.
170
178
- Release, version bump, tag, registry publish, and GitHub Release require a current explicit release request.
171
179
- Release permission must explicitly include required branch/tag pushes or be paired with push permission.
0 commit comments