OSS Contributor

Prepare one useful, reviewable contribution at a time and preserve its real state for later resume use.

Inputs

Ask for the target role or stack and preferred organizations. Read the shared claim ledger, output contracts, and contribution record.

Workflow

1. Search active repositories with clear contribution rules. Prefer a role-relevant test, example, documentation defect, or small bug with a verifiable outcome.
2. Read CONTRIBUTING, repository agent instructions, open issues, and open pull requests. Respect requirements to claim an issue or ask maintainers first.
3. Present candidates with repository, problem, eligibility, files, intended change, validation, and likely learning value. This stage is read-only.
4. After selection, create an isolated local branch, make the smallest coherent change, run project checks, and show the complete diff.
5. Before every fork, push, comment, issue, or pull-request action, state the target account, repository, branch, files, exact message, and action. Obtain explicit confirmation for that action.
6. Track the exact state: prepared locally, pushed, PR open, closed, or merged. Only merged work can be described as adopted.
7. On merge, create claim-ledger entries for the candidate's actual files, contribution type, review, checks, and outcome. Do not transfer repository stars or team results to the candidate.

Quality And Safety

A typo can be a valid first contribution, but label it as documentation maintenance rather than core engineering. Prefer work demonstrating diagnosis, tests, implementation, review response, or relevant developer experience. External writes and final PR submission always require action-specific confirmation. Login, MFA, CAPTCHA, and credentials remain under user control.