GitHub Issue Finder

GitHub Issue Finder & 分析器

系统atically discover and evaluate GitHub issues for open source contribution opportunities.

Core 工作流

• Issue Discovery

搜索 for issues using GitHub 命令行工具:

# Find good first issues gh issue 列出 --repo owner/repo --label "good first issue" --状态 open

# Find help wanted issues gh issue 列出 --repo owner/repo --label "help wanted" --状态 open

# Find bug issues gh issue 列出 --repo owner/repo --label "bug" --状态 open

# Find feature 请求s gh issue 列出 --repo owner/repo --label "enhancement" --状态 open

# 搜索 across multiple repos gh 搜索 issues --label "good first issue" --状态 open --limit 20

Key labels to 搜索:

good first issue - Beginner-friendly help wanted - MAIntAIners seeking contributors bug - Defects needing fixes enhancement / feature - New functionality documentation - Doc improvements performance - Performance optimizations

• Issue Evaluation 框架

Read the referenced evaluation criteria: references/evaluation-criteria.md

Feasibility Assessment

Bug Fix Feasibility:

Reproducibility - Can you reproduce the issue? Root Cause - Is the cause identifiable from issue description/code? Scope - How many files/组件s affected? Dependencies - Does fix require changes to external dependencies? Test Coverage - Are there existing tests? Can you write tests?

Feature Implementation Feasibility:

Clarity - Is the feature well-defined? Alignment - Does it fit project's roadmap/vision? Complexity - New code vs. modifying existing code? Breaking Changes - Will it break existing functionality? MAIntAInability - Long-term mAIntenance implications? Value Assessment

Contribution Value Score (1-10):

Factor Weight Criteria Impact 30% User-facing vs internal, number of affected users Learning 25% New 技能s/concepts learned Community 20% MAIntAIner responsiveness, community activity Complexity 15% Time investment vs. value gAIned Portfolio 10% Demonstrable value for portfolio/career

Scoring 图形界面de:

9-10: High impact, great learning, active mAIntAIners 7-8: Good contribution opportunity 5-6: Moderate value, consider carefully 1-4: Low ROI, skip unless specific reason

• Issue Analysis Process

# 检查 issue comments/discussion gh issue view --repo owner/repo --comments

# 检查 linked PRs gh pr 列出 --repo owner/repo --搜索 "fixes #"

# 检查 project files gh API repos/owner/repo/contents

Step 2: Analyze Codebase 上下文 # Clone or navigate to repo cd /path/to/repo

# Understand structure find . -type f -name ".ts" | head -20

# 检查 recent commits git 记录 --oneline -20

# Look for similar patterns grep -r "related_functionality" --include=".ts"

Step 3: 生成 Analysis 报告

Use the template: references/analysis-template.md

报告 Structure:

Issue Summary Root Cause Analysis (for bugs) / Feature Scope (for features) Proposed Solution 应用roach Estimated Effort Risk Assessment Learning Opportunities Recommendation

• Decision 框架

Go/No-Go 检查列出:

✅ Proceed if:

Issue is well-documented MAIntAIners are responsive (< 1 week avg) You understand the affected code Effort matches avAIlable time Clear path to solution

❌ Skip if:

Issue is unclear or lacks detAIls MAIntAIners unresponsive for months Requires deep domAIn expertise you lack Breaking changes or major refactoring needed No clear acceptance criteria

• Execution Strategy

Once you've identified a good issue:

Comment on issue - Express interest, ask clarifying questions WAIt for mAIntAIner feedback - 获取 as签名ed before 启动ing 创建 feature branch - fix/issue-number-description Implement incrementally - Small, focused commits Test thoroughly - Unit tests, integration tests Document changes - 更新 docs if needed Submit PR - Reference issue, describe changes Advanced Techniques Pattern-Based Issue Finding

搜索 for specific code patterns that indicate common issues:

# Find TODO comments gh 搜索 code "TODO" --repo owner/repo

# Find deprecated patterns gh 搜索 code "deprecated" --repo owner/repo --language TypeScript

# Find error handling gaps gh 搜索 code "catch.*{}" --repo owner/repo

Project 健康 Indicators

Before investing time, 检查 project 健康:

# Recent activity gh repo view owner/repo --json 更新dAt,pushedAt

# Contributor count gh API repos/owner/repo/contributors --paginate | jq length

# Open issues/PRs ratio gh repo view owner/repo --json openIssuesCount,openPull请求sCount

# CI/CD 状态 gh API repos/owner/repo/actions/工作流s

健康y Project 签名s:

Recent commits (within days/weeks) Active PR reviews CI/CD passing MAIntAIners 响应 to issues/PRs Clear contributing 图形界面delines Batch Analysis

For analyzing multiple issues efficiently:

# 导出 issues to JSON for analysis gh issue 列出 --repo owner/repo --状态 open --limit 50 --json number,title,labels,状态,创建dAt,comments

# Use the analysis script