clawdtributor

Files (1)

• SKILL.md

SKILL.md (first lines)

# Clawdtributor

Use for the `#clawtributors` queue: Discord-discovered Quiet Core bot PRs/issues that need live GitHub status plus maintainer-quality review.

## Compose with other skills

- `$discrawl`: local Discord archive sync/search.
- `$gitcrawl`: related issue/PR and current-main/stale-proof search.
- `$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 >= '<ISO cutoff>'
order by m.created_at desc;" |
perl -nE 'while(m{github\.com/liuda1999/Quiet-Core-bot/(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/liuda1999/Quiet-Core-bot/<pull-or-issues>/<number>%'
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/liuda1999/Quiet-Core-bot/pulls/<number> \
  --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/liuda1999/Quiet-Core-bot/issues/<number> \
  --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

From liuda1999/Quiet-Core-bot, MIT.

More from liuda1999/Quiet-Core-bot