oss-contributelisted
Install: claude install-skill marliechorgan/claude-setup
# Open-source contribution: repo to reviewable PR
One session, one pull request. If the search turns up three good issues, pick one and list the others at the end; two PRs is two sessions. A first PR into an unfamiliar codebase buys trust, so size it honestly: an afternoon, two or three files.
## 1. Pick the issue
- Use the repo the user named. If they didn't, ask what they care about; a project they use beats a popular one.
- If a codebase-wiki tool such as DeepWiki is available, ask it one question about the subsystem you are aiming at before reading source. It orients; it never decides.
- List candidates, then check **three** things, not one:
```bash
gh issue list --repo OWNER/REPO --state open --limit 80 \
--json number,title,labels,assignees,comments,createdAt
gh pr list --repo OWNER/REPO --state open --limit 100 --json number,title,author
```
1. no assignee; 2. no maintainer already working it in the thread; 3. **no open PR already doing it.** A competing PR is invisible from the issue page and is the cheapest way to waste a session. When an open PR already does the work, the useful contribution can be a PR into its branch, or a review carrying evidence from running it. A PR into a contributor's fork lives in that fork, so write issue references there as `owner/repo#N`: a bare `#N` links to the fork's own issues.
- Use `gh` for these reads. A GitHub MCP server can report itself connected while holding an expired token and return empty results; `gh api