Contributor pipeline gardening — awesome-claude (HeyClaude)

Contributor pipeline gardening — awesome-claude (HeyClaude)

HeyClaude is a curated registry/directory of Claude and AI-workflow assets, plus the website (apps/web), registry/schema library (packages/registry), and MCP package (packages/mcp) that serve it. This is a much smaller, quieter repo than loopover/metagraphed — as of 2026-07-17 it had zero open gittensor:*-labeled issues and a thin, fully-closed 2-milestone history. This skill exists to build and then maintain a small, deliberately curated backlog — 15-25 contributor-available issues, not 50-100 — because padding a codebase this size to a larger number would mean weak/duplicate issues, which is explicitly worse than a smaller real backlog here.

The one thing this skill exists to prevent

Confirmed by the maintainer, 2026-07-17: contributors here have recently gravitated to test(...): cover X PRs — real tests, but zero behavior change, added purely to nudge Codecov's codecov/patch: 70% bar (a soft, easily-hit target — unlike loopover's 99% gate, 70% patch coverage is trivially satisfied by testing already-written code). A second anti-pattern found during this skill's initial research: issue #550 (a "growth sprint" umbrella with a long child checklist) was being farmed almost entirely for its single easiest repeatable pattern — wiring one more page into the existing intent-event/analytics-click convention, dozens of near-identical PRs (#5205, #5202, #5201, ... #5168, all Made with Cursor), rather than any of the umbrella's harder, more valuable child issues.

Never generate a standalone test(...): cover X issue. A regression test attached to a real bug fix is fine and expected (see the template in reference.md); a test-only issue with no behavior change is not. Never generate more instances of an already-being-farmed shallow repeatable pattern (check open issues and recent merged-PR titles for a dense run of near-identical titles before filing anything that looks like "wire pattern X into one more file/page/route" — if 5+ near-identical PRs already exist for the same pattern, that vein is farmed out, not a gardening opportunity). The whole point of this skill is issues that "drive real value... website/content/features grow... fix bugs/issues in frontend/backend" (the maintainer's own words) — not more of what a low-effort automated farmer already does better and faster than a well-scoped issue ever could.

Scope: code only, not content submissions

content/ (the curated directory entries themselves) is a legitimate, real contribution surface per .gittensory.yml's wantedPaths — but content submissions are explicitly PR-first, with linkedIssuePolicy: optional and issueDiscoveryPolicy: discouraged, routed through a private submission gate that doesn't need or want a GitHub issue first. **This skill does not generate