Thanks for considering a contribution — whether it is a typo fix, a workflow suggestion, or a reuse report from your own repository, every bit helps improve the kit for the next maintainer.
Not sure where to start? The single most useful contribution is a reuse report: try the kit in a real repository and tell us what you kept, cut, or rewrote. That kind of field feedback shapes the next release more than anything else.
You can open a reuse report directly from the issue templates.
- Run
npm test. - Run
npm run validate:repo. - Update documentation when repository behavior or templates change.
Good contributions include:
- improving maintainer-facing documentation
- strengthening validation or release workflows
- improving repository templates
- clarifying issue intake or review rules
- improving support routing or maintainer help paths
- expanding examples with real OSS maintenance scenarios
- making the maintainer-layer value easier to understand for small public projects
Out of scope by default:
- product features unrelated to OSS maintenance
- opaque automation with no public explanation
- changes that weaken repository transparency
- keep changes focused
- explain maintainer impact
- call out follow-up tasks if the work is partial
- update
CHANGELOG.mdwhen behavior changes