contributor

# Contributor Automated open source contribution workflow that takes you from a GitHub repo URL to merged PRs, with built-in safeguards against common contribution failures. ## Why this skill exists Open source contributions fail for predictable reasons: fixing in the wrong layer (your PR gets closed because the maintainer preferred an upstream fix), colliding with other contributors, not following project conventions, or over-engineering a simple fix. This workflow prevents each of those failures through systematic pre-checks. ## Phase 1: Reconnaissance Before writing any code, gather intelligence about the project and its contribution landscape. ### 1.1 Identify the target Ask the user for: - The GitHub repo URL (e.g., `pydantic/pydantic-ai`) - Their GitHub username and email for commits - Any specific issue they want to work on (or ask to scan for available ones) ### 1.2 Scan for available issues Use `gh` CLI to find issues worth contributing to: ```bash # Get open issues with metadata gh issue list -R <owner>/<repo> --state open --limit 50 \ --json number,title,labels,assignees,comments # Check for competing PRs on each candidate gh pr list -R <owner>/<repo> --state open \ --search "<issue_number> in:title,body" ``` **Filter criteria** (apply in order): 1. No assignee 2. No open PR already fixing it (check both linked PRs and title/body search) 3. Fewer than 5 competing PRs 4. Prefer labels: `bug`, `good first issue`, `help wanted` 5. Prefer issues with ma...