- Home
- Skills
- Wdm0006
- Python Skills
- Community
community_skill
- Python
6
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill wdm0006/python-skills --skill community- SKILL.md2.7 KB
Overview
This skill builds and manages open source Python library communities by providing ready-made CONTRIBUTING and CODE_OF_CONDUCT files, issue and PR templates, label conventions, and GitHub automation for first-time contributors. It streamlines contributor onboarding, enforces basic governance, and automates welcome flows so maintainers can focus on code and reviews. The setup targets predictable contributor experience and clear expectations.
How this skill works
The skill generates and installs standard community files (CONTRIBUTING.md, CODE_OF_CONDUCT.md), adds structured issue and pull request templates, and defines common labels for triage. It can scaffold GitHub Actions for automating first-interaction messages and other simple workflows. Maintainable checklists and governance guidance help projects keep response time goals and contributor recognition practices consistent.
When to use it
- Initializing a new Python library to ensure clear contributor onboarding.
- Improving an existing project that lacks contributor docs or templates.
- Standardizing multiple repositories across an organization.
- Automating initial contributor interactions and PR triage.
- Establishing basic governance and contributor recognition processes.
Best practices
- Include a Contributor Covenant CODE_OF_CONDUCT.md to set behavioral expectations.
- Make CONTRIBUTING.md explicit: development setup, branch/commit guidance, test/lint steps.
- Provide clear, minimal issue and PR templates to speed triage and reviews.
- Use labels like 'good first issue' and 'help wanted' and keep them documented.
- Automate friendly first-PR messages but avoid excessive bots on repeated contributors.
Example use cases
- Scaffold CONTRIBUTING.md and ISSUE_TEMPLATE files when creating a new project repository.
- Add a welcome GitHub Action to thank and guide first-time PR authors.
- Audit an existing repo to add missing templates, labels, and a CODE_OF_CONDUCT.md.
- Define response time goals (e.g., respond to issues within 48 hours) and add them to governance.
- Set up a contributor recognition section to highlight top contributors in release notes.
FAQ
No, but Contributor Covenant is a widely adopted, community-vetted standard that covers common conduct scenarios. You can adapt it to your project's needs.
Can the templates be customized per project?
Yes. Templates are meant to be concise starting points; tailor the reproduction steps, environment details, and checklists to your codebase and workflow.