community-sweep
Land community pull requests as the contributor and answer community issues on thedotmack/claude-mem. Takes stock of every open PR (the owner's own included, except the ones the owner marked experimental) and community issue, triages each against the owner's merge philosophy and the cmem.ai hosted-s…
Install / Use
npx skills add thedotmack/claude-mem --skill community-sweepInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of community-sweep
community-sweep scores 100/100 on our quality scale, 7th of 4,704 Development & Engineering skills we index (top 1%).
Its SKILL.md is 31 KB long, well organised into 15 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
With 116,790 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 3 days ago, so community-sweep is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
community-sweep compared with similar skills
community-sweep has the highest quality score among these 4 similar skills, though 3 alternatives have been updated more recently.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| community-sweep (this skill)by thedotmack | 100 | 116.8k | 3d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install community-sweep?
- Run
npx skills add thedotmack/claude-mem --skill community-sweep. The install tabs above show the steps for each supported agent. - Which AI agents does community-sweep work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is community-sweep safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is community-sweep still maintained?
- The repository was last updated 3 days ago, so community-sweep is actively maintained.
Skill content
View source on GitHubname: community-sweep description: Land community pull requests as the contributor and answer community issues on thedotmack/claude-mem. Takes stock of every open PR (the owner's own included, except the ones the owner marked experimental) and community issue, triages each against the owner's merge philosophy and the cmem.ai hosted-service boundary, finishes somewhat-aligned PRs on the contributor's own branch, squash-merges so the contributor stays the commit author on main, thanks them by name, closes fixed issues with credit to reporter and fixer, keeps the private ledger and contributor roster current, and reports what it decided. Use when asked to "go through the PRs", "merge contributor PRs", "help contributors with their PRs", "land the new community PRs", "triage new issues and PRs", "run the community sweep", "keep the momentum", or "grow the community".
Community Sweep
Grow the claude-mem community by merging people in. Every valuable contribution lands as the contributor: their PR, their name as the commit author on main. A PR that is only partly right gets finished on their branch instead of rejected. Issues get the same treatment, so the person who reported a bug and the person who fixed it both hear about it, by name.
This is the protocol from the 2026-09-30 open-PR merge sweep, which took 257 open PRs to 46 and merged 143 contributor PRs from 87 authors with their authorship intact. It is written down so every new batch of PRs and issues gets handled the same way.
The owner's merge philosophy
- Merge as many valuable contributions as possible. This is looser than the Merge Clinic (#3372,
docs/merge-rubric.md). Opt-in features are welcome, as are extensibility (providers, hosts, hooks, settings knobs) and anything that cuts token spend (bounding, batching, dedup, filtering). - Finish, don't reject. If the intent is right but the fix is partial or buggy, finish it on the contributor's branch, or land only its additive piece (a trim). Either way the credit stays with them.
- No band-aids, but no bleeding. A fix walks the issue down to its root cause. A band-aid that stops active user harm ships only with a written post-plan: the root-cause follow-up, specified well enough to execute.
- The contributor is the author. A merge that puts the maintainer's name on someone else's work is a failed merge.
- Respect the hosted-service boundary (step 2). A PR may not change how cmem.ai cloud sync or the gateway's sign-in and trial path behave. You decide: trim or rework that part out and land the rest, or decline it with the reason.
- Security and privacy regressions block a merge. That covers secrets in logs, data sent to third parties, and injection.
- Critical bug fixes ship now. A PR that fixes a break users are hitting goes out right away, so nobody's service stays interrupted: sign-in or activation that errors, a worker that won't start, hooks that fail, capture or search that stops working, data loss. It lands first in the run and a patch release follows (step 3). It never waits for the owner, including when the broken path is cmem.ai sign-in, sync or the gateway. The boundary in step 2 covers changes to how those paths behave, not fixes that make them work again. On 2026-11-07 the owner was wrongly asked about #5455, which fixed Pro sign-in returning 500 on every install.
- Nothing needs the owner. The owner set this on 2026-11-07. Every PR and issue in a sweep gets decided and carried through by you: merge, close, release, X post. The report says what you decided and why. It never asks the owner a question or lists decisions for them.
Count humans, not tools. A PR written with Claude, Codex, Cursor or Copilot is credited to the human who opened it. Bot PRs (PostHog, Copilot agent, Dependabot) land on merit, but they never go on the roster.
Private state: never commit, never upload
Run state lives in the main checkout's gitignored .scratch/, so every worktree shares it:
MAIN_CHECKOUT="$(cd "$(git rev-parse --git-common-dir)/.." && pwd)"
STATE="$MAIN_CHECKOUT/.scratch/community"
RUN_ID="CS-$(date -u +%F)"; RUN="$STATE/runs/$RUN_ID"; mkdir -p "$RUN"
| File | What it is |
|---|---|
| $STATE/ledger.tsv | One row per outcome. The last row for a number wins. It is the source of truth for what already happened; never redo a number it shows as done. |
| $STATE/ROSTER.md | Every human with a merged PR or a co-author credit, kept for the owner's outreach. It holds emails, so never commit it, upload it, or quote it. |
| $RUN/ | This run's snapshots, triage reports, test baseline and REPORT.md. |
To append a ledger row (tab-separated; PR and issue numbers share one namespace):
printf '%s\t%s\t%s\t%s\t%s\t%s\t%s\t%s\n' "$(date -u +%FT%TZ)" <number> "$RUN_ID" <action> <merge_sha|-> <author> <coauthors|-> "<one-line note>" >> "$STATE/ledger.tsv"
- Actions for PRs:
merged,closed,blocked,skipped; for the owner's PRs, alsoexperimental, andapproved, which the owner writes to take a PR out of experimental. Older runs also wroteheld, andapprovedfor owner sign-offs. - Actions for issues:
issue-closed,issue-answered,issue-routed. Older runs also wroteissue-held. - New ledger: if
ledger.tsvdoesn't exist, create it with the headerts pr phase action merge_sha pr_author coauthors note(tab-separated).
1. Take stock
gh pr list --repo thedotmack/claude-mem --state open --limit 500 --json number,title,author,isDraft,createdAt,updatedAt,mergeable,mergeStateStatus,maintainerCanModify,headRefName,headRepositoryOwner,baseRefName,additions,deletions > "$RUN/open-prs.json"
gh issue list --repo thedotmack/claude-mem --state open --limit 500 --json number,title,author,createdAt,updatedAt,labels,comments > "$RUN/open-issues.json"
Put every open PR in exactly one bucket, using its last ledger row. Use the first bucket that matches:
| Bucket | Rule | What to do |
|---|---|---|
| Experimental | the owner's PR, last row is experimental | Leave it alone. Report any new activity. |
| Held | last row is held (written before 2026-11-07) | Triage it from scratch this run and settle it yourself, like a new PR. |
| Approved | last row is approved (the owner took it out of experimental, or an older run recorded an owner sign-off) | Triage it from scratch this run, like a new PR. |
| Blocked | last row is blocked | Re-triage only if the author pushed or replied after that row. |
| Done | last row is merged or closed | It shouldn't be open, so find out why. |
| New | no row | Triage it (step 2). |
For issues, skip the maintainer-authored ones: the [plan-NN] masters and the Merge Clinic. Triage every other open issue that:
- has no ledger row, however old it is (a run that stopped early leaves these behind);
- has
issue-heldas its last row (written before 2026-11-07): triage it from scratch this run, like a held PR; - was updated after its own last ledger row.
On a first run, that is all of them.
Test baseline. Take it once per run, before landing anything. Use a clean origin/main worktree and the same Bun as CI (bun-version: latest), because an older local Bun can fail subprocess tests that CI passes. If local Bun is behind, run every suite in the run (baseline, per-PR and gate) as npx -y bun@<latest> test …. npm view bun version gives the latest version.
npm install --no-audit --no-fund && npm run build
env -u CLAUDE_MEM_LLM_TIMEOUT_MS bun test tests > "$RUN/baseline-suite.log" 2>&1; echo "suite exit $?"
grep -E '^\(fail\)' "$RUN/baseline-suite.log" | sed -E 's/ \[[0-9.]+m?s\]$//' | sort -u > "$RUN/baseline-failures.txt"
tail -n 40 "$RUN/baseline-suite.log" | grep -E '^ *[0-9]+ pass$|^ *[0-9]+ fail$|^Ran [0-9]+ tests across'
The last command must print the suite's own summary: N pass, N fail and Ran N tests across M files, with M close to the number of test files. If it prints nothing, the run died before finishing (a crash, a timeout, a missing dependency) and an empty baseline-failures.txt means nothing. Stop, fix the cause, and take the baseline again; never land PRs against an incomplete one. A nonzero exit on its own is not that: failing tests exit nonzero, and some Bun versions crash at exit after printing the summary. The sed drops each failure's timing so the lists compare line for line.
2. Triage each new PR (read-only)
gh pr view <N> --repo thedotmack/claude-mem --json title,body,author,headRefOid,headRefName,headRepositoryOwner,maintainerCanModify,mergeable,mergeStateStatus,isDraft,closingIssuesReferences,commits,files
gh pr diff <N> --repo thedotmack/claude-mem
gh pr checks <N> --repo thedotmack/claude-mem
gh api repos/thedotmack/claude-mem/pulls/<N>/comments --paginate # inline review findings (Greptile, Cursor Bugbot, CodeRabbit)
gh api repos/thedotmack/claude-mem/issues/<N>/comments --paginate # the conversation
Read main's code with git show origin/main:<path>. Leave generated bundles out of diff sizing (the list is in step 3); they're noise and get stripped at merge. If the PR maps to a plan master (plans/NN-*.md), read that section first. A PR that implements the master's intended fix is a strong candidate. A PR that contradicts the master needs a reason.
Evidence per PR:
- Facts: author, draft,
mergeable,maintainerCanModify, CI state, non-bundle diff size, linked issues. - CI: a failure that also shows up on main's recent runs (
gh run list --repo thedotmack/claude-mem --branch main --limit 5) is not the PR's. - Root cause and change: the root cause in one or two lines, and what the PR changes.
- Still needed on main? Cite
file:lineor a commit as evidence. - Review findings: unresolved bot and maintainer findings (P0/P1/P2), and whether the contributor addressed them.
- Quality: tests added, and whether it's a band-aid.
- Boundary flags.
- Overlaps: other PRs on the same area, including maintainer PRs.
- Verdict and confidence.
Verdicts (exactly one per PR):
| Verdict | Meaning | What happens |
|---|---|---|
| MERGE | Correct, complete and aligned; mergeable now or after a mechanical merge of main | Land it (step 3). |
| MERGE+POSTPLAN | Stops real bleeding but isn't the root fix | Land it and write the post-plan into the report. |
| REWORK | Right intent, but incomplete, buggy or a band-aid | A numbered gap list is the spec. Finish it on their branch (step 4), then land it. |
| TRIM | Only part of it is additive | Keep that part on their branch and land it as their PR. Say what was dropped and why. |
| CONSOLIDATE→#M | Overlaps #M | Prefer landing the additive piece as its own trimmed PR. Otherwise fold it into #M with credit (step 4). |
| SUPERSEDED | main already fixes it | Cite the commit or file:line. Close with precise credit. |
| BOUNDARY | Crosses the hosted-service boundary as written | Trim or rework the boundary-crossing part out on their branch and land the rest, or decline it with the reason if nothing else is left. |
| DECLINE | Wrong direction, harmful, not worth finishing, or does nothing (a no-op change) | Close with thanks and the reason yourself. Never hand the owner a decision to not merge something useless. |
| SPAM / EMPTY | Unrelated to claude-mem, or no code. This includes rewrites of SECURITY.md, README or LICENSE with someone else's details, and CLAUDE.md or AGENTS.md replaced with a tool's generated output | Close with one neutral line. |
The owner's own PRs (author thedotmack)
The owner's PRs go through the same triage and landing as everyone's.
- Experimental. The owner marks a PR
experimentalin the ledger. It stays out of the sweep until the owner takes it out of experimental by writing anapprovedrow, which puts it in the Approved bucket; each run, list any new activity on it. - A boundary change in the own
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
