GitHub Bounty Hunter Kit

SKILL.md

---
name: github-bounty-hunter
description: Automatically find, analyze, and submit PRs for GitHub issues with bounties. Use when asked to find paid GitHub issues, hunt bounties, make money from open source, find good-first-issues with rewards, or submit PRs for money. Triggered by: "find bounties", "hunt GitHub issues", "make money from GitHub PRs", "find paid issues", "claim bounty".
---

# GitHub Bounty Hunter

Find and solve GitHub issues that pay bounties. Submit quality PRs and get paid.

## Core Workflow

1. **Find bounty issues** using the included bounty-finder script
2. **Verify bounty legitimacy** and competition level
3. **Assess repo compatibility** (fork, clone, implement)
4. **Submit PR** via GitHub API (REST, no git clone needed)
5. **Track PR status** and respond to review comments

## Finding Bounty Issues

Run the bounty finder:
```bash
node scripts/bounty-finder.js [platform] [min-bounty]
```

Platforms: `illbnm` (homelab-stack, $50-300/bounty), `opire` (opire.io), `claudi-builders` (claude-builders-bounty)

Example:
```bash
node scripts/bounty-finder.js illbnm 100
```

Manual search: Look for repos with `bounty` label, issues with `$` amounts in title, or bounty platform repos.

## Key Bounty Repos (High Value)

| Repo | Bounty Range | Competition |
|------|-------------|-------------|
| illbnm/homelab-stack | $50-300 USDT | HIGH (5-8 PRs/issue) |
| claude-builders-bounty | $25-200 | MEDIUM |
| TechGuyTest/* | $20-100 | LOW |

## Before Working an Issue

### Required: Check Competition
```bash
node scripts/check-competition.js [owner] [repo] [issue-number]
```
This shows how many other PRs exist for the same issue.

### Assessment Checklist
- [ ] Is this a legitimate bounty (has $ amount)?
- [ ] How many other PRs are already submitted?
- [ ] Is the issue still open and unassigned?
- [ ] Can you genuinely complete this in 2-4 hours?
- [ ] Is the bounty amount worth the effort?

## Implementing and Submitting

### Step 1: Fork the repo (via GitHub API)
```javascript
POST /repos/:owner/:repo/forks
```

### Step 2: Get issue details
```javascript
GET /repos/:owner/:repo/issues/:number
```

### Step 3: Get file contents for modification
```javascript
GET /repos/:owner/:repo/contents/:path?ref=:branch
```
Returns base64-encoded content.

### Step 4: Make changes and create commit
```javascript
POST /repos/:owner/:repo/git/blobs  // create new file blob
POST /repos/:repo/:owner/:git/trees  // create tree
POST /repos/:owner/:repo/git/commits  // create commit
PATCH /repos/:owner/:repo/git/refs/heads/:branch  // update branch
```

### Step 5: Create PR
```javascript
POST /repos/:owner/:repo/pulls
```
With title: `[BOUNTY $X] Issue Title` to make it clear.

## PR Submission Script

Use `scripts/pr-submitter.js`:
```bash
node scripts/pr-submitter.js [owner] [repo] [issue-num] [commit-sha] [title]
```

## Critical Rules

1. **Quality over quantity** - One merged PR > 10 rejected PRs
2. **Check for CLA** - Google/Microsoft repos often require CLA (blocks merge)
3. **Don't spam** - If issue says "good first issue", one agent should do it
4. **Respond to reviews** - Check PR comments daily, fix requested changes
5. **No competing if others already delivered** - Check existing PRs before starting

## Competition Strategy

- **Empty competition**: If <2 PRs and you can do it well → do it
- **Medium competition**: If 2-3 PRs and yours is clearly better → do it  
- **Heavy competition**: If >4 PRs → skip, find another issue
- **Always**: Make your PR clearly better (docs, tests, clean code)

## Payment Collection

After PR merges, payment typically comes via:
- **USDT TRC20**: Provide your wallet address in PR comment (0x...)
- **GitHub Sponsors**: The repo owner will reach out
- **Token rewards**: Check if repo has a token for rewards

Wallet for payments: `0x417fd2884CdCF751EDF351eeC07a9fdf06f8Fd32`

## Quick Commands

```bash
# Find all illbnm bounties
node scripts/bounty-finder.js illbnm 0

# Check competition for issue #12
node scripts/check-competition.js illbnm homelab-stack 12

# Submit PR after implementation
node scripts/pr-submitter.js [owner] [repo] [issue-num] [commit-sha] [title]
```

For detailed bounty platform info, see `references/bounty-platforms.md`.