--- name: clawdtributor description: "Use for OpenClaw clawtributors PR/issue triage: Discrawl discovery, live-open rechecks, deep review, topic grouping, and compact @handle/LOC/type/blast/verification summaries." --- # Clawdtributor Use for the `#clawtributors` queue: Discord-discovered OpenClaw PRs/issues that need live GitHub status plus maintainer-quality review. ## Compose with other skills - `$discrawl`: local Discord archive sync/search. - `$openclaw-pr-maintainer`: live GitHub PR/issue review, duplicate search, close/land rules. - `$gitcrawl`: related issue/PR and current-main/stale-proof search. - `$openclaw-testing` / `$crabbox`: proof choice when a candidate needs real validation. ## Archive flow Local archive first; verify freshness for current questions. ```bash discrawl status --json discrawl sync ``` Resolve channel if needed: ```bash sqlite3 "$HOME/.discrawl/discrawl.db" \ "select id,name from channels where name like '%clawtributor%' order by name;" ``` Current known channel id from prior work: `1458141495701012561`. Re-resolve if it stops matching. Extract recent refs: ```bash sqlite3 "$HOME/.discrawl/discrawl.db" " select m.created_at, coalesce(nullif(mm.username,''), m.author_id), m.content from messages m left join members mm on mm.guild_id=m.guild_id and mm.user_id=m.author_id where m.channel_id='1458141495701012561' and m.created_at >= '' order by m.created_at desc;" | perl -nE 'while(m{github\.com/openclaw/openclaw/(pull|issues)/(\d+)}g){say "$1\t$2\t$_"}' ``` Map a PR/issue back to the Discord handle: ```bash sqlite3 -separator $'\t' "$HOME/.discrawl/discrawl.db" " select m.created_at, coalesce(nullif(mm.username,''), nullif(mm.global_name,''), m.author_id) from messages m left join members mm on mm.guild_id=m.guild_id and mm.user_id=m.author_id where m.channel_id='1458141495701012561' and m.content like '%github.com/openclaw/openclaw//%' order by m.created_at desc limit 1;" ``` Show only `@handle` in the final list. Do not write the word Discord unless the user asks for source details. ## Live GitHub recheck Always recheck live state before listing, closing, or saying "open". ```bash GITHUB_TOKEN= GITHUB_TOKEN_NODIFF= GH_TOKEN= \ gh api repos/openclaw/openclaw/pulls/ \ --jq '. | {number,title,state,merged,mergeable,draft,author:.user.login,url:.html_url,updatedAt:.updated_at,additions,deletions,changedFiles:.changed_files}' ``` For issues: ```bash GITHUB_TOKEN= GITHUB_TOKEN_NODIFF= GH_TOKEN= \ gh api repos/openclaw/openclaw/issues/ \ --jq '. | {number,title,state,author:.user.login,url:.html_url,updatedAt:.updated_at,pull_request}' ``` If `gh` says bad credentials, clear env vars with empty assignments as above. Use `--jq '. | {...}'` for object projections. ## Review depth For each open item, inspect enough to classify risk: - PR body, linked issue, comments, files, additions/deletions, checks. - Current `origin/main` code path and adjacent tests. - Related threads with `gitcrawl neighbors/search`. - Whether main already fixed it, the PR is obsolete, or the idea is invalid. - Blast radius: touched runtime surfaces, config/schema, plugin/core boundary, user-visible behavior, release/package surface. - Verification: say if local unit/docs proof is enough, live/provider proof is needed, or it is not directly verifiable. Do not close from title alone. If closing as done on main or nonsensical, prove it against current main and comment first when mutation is requested. Bulk close/reopen above 5 requires explicit scope. ## Candidate selection When asked for `5 new`, exclude refs already surfaced in the session and refill from the archive until there are 5 live-open candidates. If fewer than 5 remain open, list all open ones and say how many short. When asked to `update`, `refresh`, `recheck`, `check again`, or similar, return an updated live-open candidate list. Sort by maintainer importance, not recency: high-impact ready fixes first, then useful-but-review-first, then open/not-ready items. Do not include a "changed since last pass" section or bottom-line merged/closed summary unless the user explicitly asks for churn. Prefer: - Fresh, open, external contributor work. - Small, high-confidence bugfixes. - Clear repro, tests, or obvious code-path proof. Demote: - Broad product/features without owner decision. - Large rewrites with unclear contract. - PRs already in progress, merged, closed, duplicate, or fixed on main. ## Topic grouping Group only when useful or requested: - Agents/tooling - Providers/auth/models - Channels/messaging - UI/web - Gateway/protocol/runtime - Config/memory/cache - Docker/install/release - Docs/tests/chore - Closed/obsolete Infer topic from labels, touched files, title/body, and actual code path. ## Output format No Markdown tables. Compact bullets. Use color/risk markers: - 🟢 low/narrow - 🟡 medium or needs targeted proof - 🔴 broad/high runtime risk - 🟣 security/policy/owner-boundary slow review - ✅ merged - ⚪ closed unmerged Required line shape: ```markdown - **PR #81244** `@whatsskill.` `+118/-1` `bug` 🟢 https://github.com/openclaw/openclaw/pull/81244 - Prevents chat action buttons from overlapping short assistant replies. Verifiable: yes. Blast: web chat rendering, low. - **Issue #81245** `@alice` `LOC n/a` `bug` 🟡 https://github.com/openclaw/openclaw/issues/81245 - Reports duplicate Telegram replies when reconnecting after gateway restart. Verifiable: partial. Blast: Telegram channel runtime, medium. ``` Rules: - Bold the `PR #n` or `Issue #n` marker. - Use `@handle`, not author bio text. - Always include the full GitHub URL. - Include a one-line description after the URL, separated with `-`. - PR LOC is `+additions/-deletions`; issue LOC is `LOC n/a`. - Type: `bug`, `feature`, `perf`, `security`, `docs`, `test`, `chore`, or `refactor`. - Write a full sentence for what it does. - Always include blast radius in one phrase. - Always include `verifiable: yes|partial|no` plus the shortest proof hint when helpful. - If status is not open, still show it only when the user asked for all surfaced refs; use ✅ or ⚪ and state merged/closed. - For refresh-style asks, prefer section order: `Best Open Now`, `Useful But Review First`, `Still Open / Not Ready`. Omit merged/closed churn by default. --- Source attribution: ntutangyun Original project: https://github.com/ntutangyun/openclaw/blob/abfe3a4c5536d9999e37b29874477976283745c1/.agents/skills/clawdtributor/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2026 OpenClaw Foundation Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Third-party notices for incorporated or adapted code are recorded in THIRD_PARTY_NOTICES.md. # Dave AI resource metadata Creator / publisher: ntutangyun Original project: https://github.com/ntutangyun/openclaw/blob/abfe3a4c5536d9999e37b29874477976283745c1/.agents/skills/clawdtributor/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Project & Program Management, Customer Support Roles: Backend Developer, DevOps / SRE, Project Manager, QA / Test Engineer, Technical Support Specialties: API, Database, DevOps, Word Documents, Frontend, Git, Testing Tools: Discord, GitHub, SQLite Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 906bfe1cc132ccfb82bd3c374e2d011236e00b442dd2493c376a8eabbb64c14c