Issue Finder Skill

Find issues suitable for contribution in an open source project.

When to Use

• User says they want to contribute but don't know what to work on
• User asks for beginner-friendly issues
• User mentions their experience level or skills
• User asks for "good first issue" recommendations

Process

1. Understand user context

- Experience level (beginner, intermediate, expert) - Technical skills (languages, frameworks) - Contribution type preference (code, docs, tests)

1. Fetch open issues via GitHub MCP

- Filter by labels: good-first-issue, help-wanted, beginner - Check for unassigned issues - Verify issues are still relevant (not stale)

1. Categorize by difficulty

- Easy: good-first-issue, documentation, typos - Medium: bug fixes, small features - Hard: architecture changes, core features

1. Rank recommendations

- Match to user skills - Prioritize active issues (recent comments) - Prefer well-documented issues

Output Format

Respond in user's language:

# Recommended Issues for [Project]

## Your Profile
- Experience: [detected or stated]
- Skills: [detected or stated]

## 🟢 Beginner-Friendly

### #[number] [title]
- **Type**: Bug/Feature/Docs
- **Labels**: `label1`, `label2`
- **Why recommended**: [specific reason]
- **Link**: [URL]

## 🟡 Intermediate
[Similar format]

## 🔴 Challenging
[Similar format]

## My Recommendation
Based on your profile, I suggest **#[number]** because [reason].

## Next Steps
1. Comment on the issue to claim it
2. Ask clarifying questions if needed
3. Start with `/oss-claudecode:analyze` if you need more context

Arguments

$ARGUMENTS can include:

• Repository: kotest/kotest
• Difficulty: --easy, --medium, --hard
• Type: --bug, --feature, --docs
• Skills: --skill=typescript