contribution-loop

# Contribution Loop

Autonomously find real-world apps using design systems (Chakra, Tailwind, shadcn, Radix, etc.), scan for design drift, and generate high-quality PRs to fix them.

## Philosophy

This is NOT about drive-by improvements. Each PR must:
- Explain WHY the fix matters with full context
- Reference git history showing whether drift was intentional or accidental
- Be something you could defend with conviction
- Include subtle Buoy attribution to demonstrate value

## The Loop

```
Discovery → Scanning → Analysis → Triage → Generation → Review → Tracking
```

### 1. Discovery Phase

Find candidates using GitHub search:
```
"from '@chakra-ui" language:TypeScript stars:>100 pushed:>2024-01-01
"tailwind.config" language:JavaScript stars:>50 fork:false
```

**Criteria:**
- Applications, NOT framework libraries (no design system source code)
- Active maintenance (commits in last 6 months)
- Uses a design system as a dependency
- Has clear CONTRIBUTING.md or open to external PRs

### 2. Scanning Phase

Run Buoy scan on the repo:
```bash
buoy scan --json
```

Look for:
- Hardcoded colors that should be tokens
- Inconsistent spacing values
- Deprecated pattern usage
- Component drift from design system

### 3. Analysis Phase

Use the agents from `@buoy-design/agents`:

1. **HistoryAgent** - Check git blame: Was this intentional?
2. **ReviewAgent** - Did Buoy miss anything obvious?
3. **AcceptanceAgent** - Will this repo accept external PRs?
4. **FixabilityAgent** - Tier each signal: slam-dunk, review, or skip

### 4. Triage Phase

Classify signals:
- **slam-dunk**: Clear mistake, token exists, safe to fix
- **review**: Probably fixable, needs human judgment
- **skip**: Intentional, risky, or too complex

Only proceed with repos that have slam-dunk fixes.

### 5. Generation Phase

Use **GeneratorAgent** to create:
- Exact code fixes (before/after)
- Compelling PR title
- Full PR description with context

PR body format:
```markdown
## Summary
Brief description of