contributing-to-awesome-claude
SolidUse when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue comment on platform/code PRs but does not itself merge or close content PRs. Unlike JSONbored/gittensory and JSONbored/metagraphed, a linked issue is OPTIONAL here — do not import their mandatory-linked-issue rule into this repo. Invoke for any "contribute to / open a PR against / submit an entry to / fix a bug in awesome-claude (HeyClaude)" task.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- JSONbored
- Repository
- JSONbored/awesome-claude
- Created
- 12 months ago
- Last Updated
- 3 weeks ago
- Language
- MDX
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
contributor-pipeline-gardening
Maintenance of the contributor issue pipeline for JSONbored/awesome-claude (HeyClaude) — closing issues that are already done but not marked so, and keeping a small, high-value contributor-available backlog stocked with real website/content/feature/bugfix work. Runs every ~24h via a dedicated scheduled task. Invoke for "run the issue gardening", "audit open issues for stale/complete ones", "generate new contributor issues", or any recurring/scheduled run of this process. `reference.md` (next to this file) has the exhaustive label/milestone/ template detail — read it before doing real work, not just this file. This is the awesome-claude-specific instance; JSONbored/loopover and JSONbored/metagraphed each have their own separate copy with different conventions and a much larger backlog target — do not cross-apply either repo's specifics to this one without being asked.
contribute
Resolve a GitHub issue on opendatadiscovery/odd-platform end-to-end as a virtual contributor — scope, reproduce, root-cause, plan (GATE 1), change code, add unit + integration tests, update docs + ontology, open a DRAFT PR (GATE 2). Composes the ontology / test / doc / adr machinery; posts clarifying + root-cause comments via a scoped-token GitHub App; never merges.
adept-contributing
How to contribute to the adeptability (adept) Go CLI — build, the required pre-PR gates, conventional commits, and where things live. Apply when changing adept's own source, opening a PR, or adding a harness.