OSS Issue Scout

Overview

Identify contribution rules and surface a small set of high-value, maintainer-friendly issues for a given GitHub repository.

Workflow

1) Confirm inputs

• Ask for the repo URL or a local repo path and whether GitHub access is available.
• Ask for constraints: language/stack familiarity, time budget, desired impact, preferred work type (bug/doc/test/feature), and skill level.
• Ask if the user can run tests and open PRs.

2) Read contribution rules and signals

• Check repo docs locally or via GitHub: CONTRIBUTING.md, README, CODE_OF_CONDUCT, SECURITY.md, LICENSE, GOVERNANCE, MAINTAINERS, issue/PR templates, .github/ folder, CI configs.
• Note CLA/DCO requirements, branch naming, commit rules, test expectations, and required checks.
• If any open-source or GitHub practice is unclear, use Context7 to refresh before advising.