Updated 1mo ago
by chiruu12
OSS-Skills
15 executable skills that walk you through your first open source contribution. Works in Claude Code, Cursor, Codex, Copilot, Windsurf, Zed and anything that reads AGENTS.md. Built by a GSoC mentor.
60 GitHub stars (60)
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | 0 |
| Sep 30 | 0 |
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | −1 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 15 skills (15 skills found in its SKILL.md files)
- 6 forks (6 forks)
- 1mo ago last update (Last updated 1mo ago)
Install
Skills CLI
npx skills add chiruu12/OSS-Skills
Asks which skills and agents to install. Just one: npx skills add chiruu12/OSS-Skills --skill oss-contribute — add -g for every project.
Claude Code
git clone https://github.com/chiruu12/OSS-Skillscp -r "OSS-Skills/skills/oss-contribute" ~/.claude/skills/
Copies the oss-contribute skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add chiruu12/OSS-Skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
oss-contribute
Research an issue deeply and present all context to the user. but the user writes the code. The LLM investigates code paths, finds relevant files, explains patterns, and identifies constraints. The user thinks through the approach and implements it. Use when ready to start working on an issue after oss-prep-to-contribute. Not for writing tests or documentation as a standalone contribution. Use os…
skills/oss-contribute/SKILL.md on GitHub (opens in a new tab) -
oss-debug-ci
Debug CI failures in unfamiliar repo pipelines. Reads CI configs, fetches failure logs, classifies the failure type, and guides the user through diagnosing and fixing the issue. Use when CI fails on your PR in an OSS repo, when you don't understand a CI error, or when debugging GitHub Actions/CircleCI/other CI systems. Not for setting up CI from scratch — this is for debugging existing pipelines.
skills/oss-debug-ci/SKILL.md on GitHub (opens in a new tab) -
oss-evaluate-repo
Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.
skills/oss-evaluate-repo/SKILL.md on GitHub (opens in a new tab) -
oss-explore-repo
Guided codebase exploration for understanding a repo's architecture, patterns, and domain language before contributing. Not issue-specific. builds general understanding. Use when exploring a new repo, wanting to understand how a project works, or preparing to become a regular contributor. Not for learning a framework or language you have never used. Use oss-learn-stack for that.
skills/oss-explore-repo/SKILL.md on GitHub (opens in a new tab) -
oss-find-issue
Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues. Not for finding problems that nobody has filed an issue for yet. Use oss-find-real-issue…
skills/oss-find-issue/SKILL.md on GitHub (opens in a new tab) -
oss-find-real-issues
Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available. Not for browsing the existing issue tracker. Use oss-find-issue for that.
skills/oss-find-real-issues/SKILL.md on GitHub (opens in a new tab) -
oss-learn-stack
Learn unfamiliar technologies used in a repo by studying how the repo actually uses them. Finds patterns, explains concepts in context, and points to examples in the codebase. Use when a repo uses frameworks, languages, or patterns you haven't worked with before. Not for mapping a repo's architecture or domain language. Use oss-explore-repo for that.
skills/oss-learn-stack/SKILL.md on GitHub (opens in a new tab) -
oss-post-pr
Handle PR review feedback - understand reviewer comments, research their concerns, and help the user address them. The LLM explains what reviewers want and why; the user decides how to respond and writes the code. Use when you receive review comments on a submitted PR. Not for opening the PR in the first place, which is oss-submit-pr. If the feedback is a failing CI job, use oss-debug-ci.
skills/oss-post-pr/SKILL.md on GitHub (opens in a new tab) -
oss-prep-to-contribute
Prepare to contribute to an open source repo. Reads all contribution docs, checks eligibility, assesses the user's knowledge gaps, and fills them before coding starts. Use after finding an issue with oss-find-issue, or when starting work on any OSS repo. Not for installing dependencies or getting the build and tests running. Use oss-setup-dev-env for that.
skills/oss-prep-to-contribute/SKILL.md on GitHub (opens in a new tab) -
oss-review-prs
Review other contributors' PRs to learn the codebase and build maintainer trust. Guides structured diff reading, helps formulate review comments, and teaches how to distinguish blocking issues from nits. Use when you want to learn a codebase by reviewing PRs, build trust with maintainers before contributing code, or practice code review on OSS repos. Not for reviewing your own PR — use oss-submit…
skills/oss-review-prs/SKILL.md on GitHub (opens in a new tab) -
oss-second-contribution
Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-is…
skills/oss-second-contribution/SKILL.md on GitHub (opens in a new tab) -
oss-setup-dev-env
Set up a complete development environment for an unfamiliar OSS repo. Handles dependency installation, building, running tests, and configuring dev tooling. Use when cloning a new OSS repo and setting up for development, when the repo's setup instructions don't work, or when you need to debug environment issues. Not for setting up your own project — this is for getting someone else's repo running.
skills/oss-setup-dev-env/SKILL.md on GitHub (opens in a new tab) -
oss-submit-pr
Submit a pull request following the repo's contribution guidelines. Reviews the diff, checks for common rejection reasons, and helps the user write their own PR description. The LLM reviews. the user writes. Use when implementation is complete and tests pass. Not for responding to review comments after the PR is open. Use oss-post-pr for that.
skills/oss-submit-pr/SKILL.md on GitHub (opens in a new tab) -
oss-write-docs
Contribute documentation improvements to an OSS repo. Identifies doc gaps, studies the docs system, and verifies accuracy against source code. Use when contributing documentation to an open source project, fixing outdated setup instructions, adding missing API docs, or improving README clarity. Not for writing docs for your own project — this is for contributing docs to someone else's repo.
skills/oss-write-docs/SKILL.md on GitHub (opens in a new tab) -
oss-write-tests
Write tests for untested OSS code as a standalone contribution. Identifies coverage gaps, studies the repo's test conventions, and guides the user through writing tests that match existing patterns. Use when contributing tests to an open source repo, looking for a low-risk first contribution, or improving test coverage. Not for writing tests alongside a bug fix — use oss-contribute for that.
skills/oss-write-tests/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.