contribute
Skill836 starsChanged 19 days agoApache-2.0View on GitHub
Prepare a contribution to the gcx repository: report or fix a bug, update documentation, or propose and implement a code change. Use inside a gcx checkout for contribution routing, planning, implementation and self-review; operating a Grafana instance uses the portable gcx/product skills.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- gdhub-io/character-forge-mcptheir own version, first seen Nov 15, 2026
- chrisconviviera/conviviera-claude-plugintheir own version, first seen Nov 12, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- Devolutions/IronRDPtheir own version, first seen Nov 1, 2026
- inite-ai/inite-visibilitytheir own version, first seen Nov 1, 2026
- inite-ai/inite-brain-servicetheir own version, first seen Nov 1, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- mindfold-ai/Trellis★ 15ksame name
- gluestack/gluestack-ui★ 5.3ksame name
- Devolutions/IronRDP★ 3.3ksame name
- egregore-labs/egregore★ 293same name
- manor-os/manor-ai★ 158same name
- inite-ai/inite-brain-service★ 43same name
- yusukebe/skills★ 36same name
- zajca/pohunek★ 9same name
- marwan562/agents-skills★ 8same name
- jeremylongshore/contributing-clanker★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-rfcSkill
- generate-slideSkill
- propose-featureSkill
- releaseSkill
- review-prSkill
- review-rfcSkill
- update-rfcSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read AGENTS.md and the authoritative contribution workflow.
- Distinctive: line 27
Feature: use propose-feature to research and draft the common proposal.
- Distinctive: line 29
Follow AGENTS.md privacy rules.
- Distinctive: line 33
Follow CONTRIBUTING for the RFC requirement on new features and the product-team exception.
- Distinctive: line 47
Use the existing subsystem implementation for other changes.
- Distinctive: line 51
Read self-review and apply checks triggered by the actual diff, including incremental fixes.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contribute to gcx
Read AGENTS.md and the authoritative contribution workflow. Use its route and ownership guidance; the contributor does not need to choose a provider, datasource or RFC workflow upfront.
1. Establish the current step
Identify the requested outcome and the existing issue, accepted decisions, RFC or implementation branch. Inspect those records and relevant code before asking questions. State the applicable route, current step and missing maintainer decision. Reuse settled scope and design at each handoff.
Work within the request and existing authorization. A draft-only or review-only request ends with that artifact. An implementation request continues through authorized work once applicable maintainer decisions are settled. Prepare the concrete result before requesting publication permission; reuse authorization already given for the same destination and scope.
2. Prepare the issue when the route needs one
Documentation changes and bug fixes can go directly to a PR. Other code contributions need an accepted issue; comment on it to coordinate the work. Follow the product-team exception for changes within an existing owned area.
Search the repository’s open and closed issues for existing reports and proposals before creating an issue or starting implementation. Reuse a relevant issue; check its outcome and maintainer decisions before proceeding. When its maintainer decision is settled, continue to the needed planning or implementation rather than drafting another proposal.
- Bugfixes: can go directly to a PR without a separate issue or prior maintainer acknowledgement. When reporting a bug, search for an existing report first and add relevant evidence there. If no report matches, use the Bug report form. Establish actual and expected behavior, reproduction or evidence, and relevant version/environment. Link the existing report from the fix PR when available. Record verified findings separately from assumptions.
- Feature: use propose-feature to research and draft the common proposal. Show a concrete problem, proposed UX and checkable acceptance criteria; scale examples to the work and identify unresolved facts.
Follow AGENTS.md privacy rules. File or change a shared issue within publication authorization. Reuse any maintainer decisions already recorded on the issue; discuss additional design there or in the PR when no issue exists.
3. Load only the planning that is needed
Follow CONTRIBUTING for the RFC requirement on new features and the product-team exception. Use create-rfc for the required design, review-rfc for design review, and update-rfc when explicitly asked to reconcile existing implementation evidence. Reuse the issue's accepted behavior and scope.
Developers choose their own implementation and planning approach. Reuse the accepted issue and any RFC for scope and acceptance criteria. An RFC can describe the overarching design and PR sequence; straightforward slices can be tracked on the issue.
4. Implement with the appropriate references
For a bug, inspect the relevant subsystem and add appropriate regression coverage. For documentation or test-only work, inspect the affected material.
For a capability or command change, read capability implementation for placement, backend readiness and the command contract. Carry decisions into the existing planning record rather than producing another mandatory document. Then load:
- Provider implementation for a Cloud product provider, including conditional resource adapters and smoke tests.
- Datasource implementation for a new datasource kind, including shared queries, Explore links, codecs and routing.
- Distribution and gates when resource or datasource wiring, command annotations, or bundled skill coverage changes.
Use the existing subsystem implementation for other changes. Resolve routine choices from repository evidence; ask about unresolved choices that materially change scope or behavior. Preserve CONSTITUTION, DESIGN and architecture rules.
5. Verify and prepare review
Read self-review and apply checks triggered by the actual diff, including incremental fixes. Run AGENTS.md quality checks and relevant domain verification using the built binary. Report failed or unavailable checks with their reason; a test or probe that did not run is not a pass.
RFC reconciliation is a separate requested task. When an issue exists, implementation PRs reference it; the final completing PR closes it. Summarize the change, checks, unresolved assumptions and documented deviations for review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

