oss-issue-scout
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.
3) Pull issues via GitHub MCP
- Discover available GitHub MCP resources/templates and use them to list open issues with labels, assignees, milestones, and last activity.
- Prefer issues labeled good first issue/help wanted/bug/docs/tests and those with clear acceptance criteria.
- Filter out: stale/needs info, blocked, huge refactors, security-sensitive items, no reproduction steps, or already assigned issues.
- Cross-check for linked PRs, duplicates, or active discussions that indicate ongoing work.
4) Score and shortlist
- Use
references/issue-scoring.mdto score value, acceptance likelihood, clarity, and effort fit. - Select 3-7 issues with the best balance of impact and low acceptance risk; keep scope aligned to user constraints.
5) Report back
- Provide a concise list of recommended issues with links, labels, last activity, estimated effort, and why they are good picks.
- Summarize contribution rules and any blockers.
- Ask targeted questions if key info is missing or if all candidate issues are low quality.
Output format
- Recommended issues
- Contribution rules and constraints
- Risks/unknowns
- Questions for the user
- Suggested next actions
References
- Read
references/issue-scoring.mdwhen scoring or filtering issues.
More from peterfile/my-common-skills
kiro-specs
Create a Kiro spec for a feature in .kiro/specs create/update feature spec/PRD/RFC—requirements, design doc, and implementation tasks checklist.Trigger on spec/specification/PRD/RFC/tech spec, requirements/user story/acceptance criteria/EARS, design doc/architecture, task breakdown/implementation plan/checklist; 需求/验收/设计/任务.
9pnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
3canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
3turborepo
|
3typescript-write
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.
3frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
3