⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
oss-contribute
|
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
OSS-Skills
15 skills that walk you through your first open source contribution, and your tenth. Install in 30 seconds on Claude Code, Codex, Cursor, Cline, Copilot, Windsurf, Zed, Gemini CLI or Kiro. Start with oss-find-issue. The skill handles the research, you handle the thinking.
Built by a GSoC mentor who got tired of watching contributors make the same avoidable mistakes - picking issues nobody maintains, skipping CONTRIBUTING.md, submitting PRs that ignore the repo's conventions, and not being able to explain their own code during review.
These skills encode what I wish every contributor knew before their first submission.
This is NOT a curated list or a collection of resources. These are executable skills you install and run. They search GitHub issues, read contribution docs, trace code paths, check if repos accept outside contributions, and ask you questions at every step. If you want a markdown list, this isn't it.
See it work
An abridged session. The issue numbers are invented, everything else is what the skills actually do.
You: /oss-find-issue
Skill: What languages do you know? Any specific repos, or want me to find one?
You: I know Python. No specific repo - find me a good first issue anywhere.
Skill: [searches repos, checks eligibility, filters by maintainer-filed issues]
Found 3 unclaimed issues matching your skills...
1. fastapi/fastapi #5621 - Fix type hint in dependency injection
2. pallets/click #2734 - CLI argument parsing edge case
3. encode/httpx #3102 - Connection timeout not respected
You: That second one looks interesting - the CLI argument parsing bug.
Skill: Why that one? What do you think the fix involves?
(Hint: look at the scope above - what about it matches your skills?)
You: I've worked with Click before. The description mentions argument groups
which I dealt with in my last project...
Skill: Good. Re-checking nobody took it while we talked... still clear.
Some repos want a maintainer to assign instead. This one lets you
self-claim, so post a one-liner and keep it short:
"I'd like to work on this - looks like it's in the argument group
handling. Happy to take it if nobody else has started."
You: Posted.
Skill: Run /oss-prep-to-contribute next.
You: /oss-prep-to-contribute
Skill: [reads CONTRIBUTING.md, CODE_OF_CONDUCT, maps architecture]
This repo uses pytest, conventional commits, and requires DCO sign-off.
Quick check: do you know what DCO sign-off means?
You: Not really...
Skill: It's a one-line attestation that you have the right to submit this code.
Add it with: git commit -s. Here's the full guide: ...
Now explain the repo's architecture in your own words.
Install - 30 seconds
Requirements: Git, gh CLI (authenticated), and an AI coding tool.
git clone https://github.com/chiruu12/OSS-Skills.git
cd OSS-Skills
./setup
That installs for Claude Code. For anything else, name it:
./setup --target cursor # or cline, copilot, windsurf, zed, gemini, kiro
./setup --target agents # AGENTS.md, read by Codex, Aider, Goose, Amp and ~25 more
./setup --list # every target
Non-Claude targets install into the current directory, so run them from your
project, or pass --dest /path/to/project. For a project-local Claude install,
use ./setup --local.
Or paste this into Claude Code and it handles everything:
Install OSS-Skills: run
git clone https://github.com/chiruu12/OSS-Skills.git && cd OSS-Skills && ./setup
The skills
Slash syntax is Claude Code. On every other tool there is no slash command: ask your agent for the workflow by name, such as "follow the oss-find-issue workflow".
Evaluation
| Skill | Role | What it does |
|---|---|---|
/oss-evaluate-repo | Analyst | Assesses project health, governance, bus factor, community before you invest time. Prevents wasting weeks on abandoned repos |
Contribution pipeline
| Skill | Role | What it does |
|---|---|---|
/oss-find-issue | Scout | Finds unclaimed issues from maintainers, checks if repo accepts outside contributions, matches to your skills |
/oss-prep-to-contribute | Tutor | Reads all docs, maps the codebase, checks your knowledge gaps, won't let you code until you can explain the architecture |
/oss-setup-dev-env | Mechanic | Gets the repo building, testing, and linting on your machine. Reads CI config as source of truth when README is stale. IDE hints for VS Code, JetBrains, Cursor, Windsurf, Neovim |
/oss-contribute | Pair programmer | Traces code paths, finds patterns. You describe the logic, it helps you implement. Won't write code until you explain what it should do |
/oss-submit-pr | Reviewer | Pre-flight checks (tests, lint, rebase). Reviews your diff. You write the PR description, it tells you what to cut. Finds and enforces PR templates |
/oss-post-pr | Translator | Decodes terse reviewer comments. Finds codebase examples of what they want. You explain the feedback before fixing |
/oss-find-real-issues | Auditor | Finds real code problems not in the tracker (missing tests, error handling gaps). Fetches issue templates before filing. You evaluate what's worth filing |
Contribution types
| Skill | Role | What it does |
|---|---|---|
/oss-write-tests | Test author | Write tests for untested code as a standalone contribution. Highest-value, lowest-risk first contribution. Studies repo test conventions and makes you match them exactly |
/oss-write-docs | Documentarian | Contribute documentation improvements. Verifies every claim against source code, tests every example, matches the repo's docs voice |
CI and review
| Skill | Role | What it does |
|---|---|---|
/oss-debug-ci | Debugger | CI failed and the error makes no sense. Reads CI config, fetches logs, classifies failure type, determines if it's your fault or pre-existing |
/oss-review-prs | Reviewer | Review other contributors' PRs to learn the codebase and build maintainer trust. Teaches structured diff reading and comment etiquette |
Growth
| Skill | Role | What it does |
|---|---|---|
/oss-second-contribution | Coach | Your first PR merged. Now what? Plans the transition from one-off contributor to regular. Progressive complexity escalation, relationship building, community presence |
Research and learning
| Skill | Role | What it does |
|---|---|---|
/oss-explore-repo | Guide | Walks you through the architecture, domain language, and patterns of a repo. You build a mental model before picking an issue |
/oss-learn-stack | Teacher | When the repo uses tech you don't know, teaches it from the repo's own code. Every example is from the actual codebase, not generic docs |
Evaluation:
oss-evaluate-repo -> oss-explore-repo -> oss-find-issue
Learning track:
oss-explore-repo -> oss-learn-stack -> oss-find-issue (or oss-find-real-issues)
Contribution track:
oss-find-issue -> oss-prep-to-contribute -> oss-setup-dev-env -> oss-contribute -> oss-submit-pr -> oss-post-pr
| |
(alternatives) oss-write-tests / oss-write-docs |
(CI fails) oss-debug-ci
|
oss-second-contribution
// HOW IT'S BUILT
KEY FILES