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-issues for that.
chiruu12 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add chiruu12/OSS-Skills --skill oss-find-issue技能说明
name: oss-find-issue description: | 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-issues for that.
Find Issue
Find a real, unclaimed issue that matches your skills. from repos that actually want your contribution. This skill does the research; you decide what's worth your time.
Purpose
Not every issue is worth picking up. Random issues filed by drive-by users often get closed without merging. Issues from maintainers and org members are the ones that get reviewed and merged. This skill finds those, checks if the repo accepts outside contributions, and matches issues to what you actually know. so you don't waste weeks on something that gets rejected or ignored.
Prerequisites
- A GitHub account with
ghCLI authenticated - A target repo or area of interest (language, framework, domain)
Process
1. Understand the contributor
Before searching for anything, understand who's contributing. Ask the user:
- "What languages and frameworks are you comfortable with?"
- "What's your experience level? (first contribution / a few PRs merged / experienced contributor)"
- "Any specific repos or domains you're interested in? (web, CLI tools, data, infra, etc.)"
Do NOT skip this. Issue matching without knowing the contributor is useless.
2. Check contribution eligibility
Before looking at a single issue, verify the repo accepts outside contributions:
# Fetch contribution guidelines
gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/.github/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/CODE_OF_CONDUCT.md --jq '.content' | base64 -d 2>/dev/null
Check for:
- Explicit "we welcome contributions": if absent, that's a yellow flag
- CLA requirements: some orgs require signing a Contributor License Agreement before any PR
- "Internal only" signals: some repos state contributions are restricted to org members
- Stale contribution docs: if CONTRIBUTING.md references tools/processes from 3+ years ago, the repo may not be actively maintained
- Recent external PRs merged: strongest signal that outside contributions are welcome
# Check if external PRs actually get merged
gh api "repos/{owner}/{repo}/pulls?state=closed&per_page=50" \
--jq '.[] | select(.merged_at != null)
| select(.author_association != "MEMBER" and .author_association != "OWNER")
| "\(.author_association)\t\(.user.login)\t\(.title)"'
If the repo doesn't accept outside contributions, tell the user immediately and suggest alternatives. Don't waste their time.
3. Identify maintainers and core contributors
Issues filed by maintainers carry more weight. they represent actual project priorities.
# Get repo collaborators and recent committers
gh api repos/{owner}/{repo}/contributors --jq '.[0:10] | .[].login'
# Check issue author association
gh issue list -R {owner}/{repo} --state open --json number,title,author,labels,assignees,authorAssociation,createdAt --limit 50
Filter for issues where authorAssociation is OWNER, MEMBER, or COLLABORATOR. These are the issues maintainers actually care about.
4. Search for matching issues
# Good first issues from maintainers
gh issue list -R {owner}/{repo} --label "good first issue" --state open \
--json number,title,labels,assignees,comments,createdAt,authorAssociation,author
# Help wanted
gh issue list -R {owner}/{repo} --label "help wanted" --state open \
--json number,title,labels,assignees,comments,createdAt,authorAssociation,author
# GSoC-specific (if applicable)
gh issue list -R {owner}/{repo} --label "gsoc" --state open \
--json number,title,labels,assignees,comments,createdAt,authorAssociation,author
For each candidate issue, read the whole thing:
gh issue view {number} -R {owner}/{repo} --json body,comments,assignees,labels,author,authorAssociation,createdAt,updatedAt
Step 5 decides whether anyone else already has it. Do not skip ahead to ranking.
5. Rule out issues that are already someone else's
An issue somebody claimed is not available. Taking it anyway costs more than the merge is worth: maintainers notice, and the contributor you raced remembers. Run every check below on each candidate. Any one of them hitting means drop the issue and move on.
# Assignees, labels, and every comment. Not just the recent ones.
gh issue view {number} -R {owner}/{repo} \
--json state,assignees,labels,comments,author,authorAssociation
# Cross-referenced pull requests. This is the check people skip, and it is the
# one that catches someone who opened a PR without ever commenting.
gh api repos/{owner}/{repo}/issues/{number}/timeline --paginate \
--jq '.[] | select(.event == "cross-referenced") | .source.issue
| select(.pull_request != null)
| "\(.state)\t\(.repository.full_name)#\(.number)\t\(.user.login)"'
That prints state, source repo, and author for every referenced PR. Cross-repo
references are noise: a fork or an unrelated project mentioning the issue does
not claim it. Only rows from {owner}/{repo} count.
Drop the issue if any of these is true:
| Signal | What to look for |
|---|---|
| Assigned | Any assignee who is not the user and is not a bot |
| Reserved by label | assigned, claimed, taken, in progress, wip, has-pr, pr-open, or whatever the repo uses locally |
| Claimed in a comment | Read every comment, oldest to newest: "I'll take this", "can I work on this", "please assign me", "/assign", |