issue-maker

# Issue-Maker

Turn any user request into GitHub issues following team conventions.

---

## Hard Rules

1. **Repo:** `pollinations/pollinations`
2. **Assignee:** Assign to appropriate team member based on domain expertise
3. **No local side-effects** (no file creation/modification)

---

## Workflow

### 1. Research First

Before creating any issues:

```bash
# Check @eulervoid's PRs for style inspiration (concise, bullet-point format)
gh search prs --repo pollinations/pollinations --author eulervoid --limit 5

# Search existing issues for patterns
gh search issues --repo pollinations/pollinations "KEYWORD" --limit 5
```

### 2. Plan

List all planned issues:

-   One sentence description per issue
-   Identify assignee and labels
-   Note related PRs or issues

### 3. Create

```bash
gh issue create --repo pollinations/pollinations \
  --title "EMOJI Short clear title" \
  --body "- Bullet point 1
- Bullet point 2
- Bullet point 3" \
  --assignee HANDLE \
  --label "LABEL"
```

### 4. Output

Provide Discord-compatible summary:

-   Bold titles with issue numbers
-   Plain URLs on separate lines (Discord auto-embeds)
-   Group by category

---

## Team Handles

| Name   | GitHub          | Domain                    |
| ------ | --------------- | ------------------------- |
| Thomas | **@voodoohop**  | General, Models, Infra    |
| Joshua | **@eulervoid**  | Pollen, Backend, Auth     |
| Elliot | **@elliotetag** | Community, Newsletter, UI |

---

## Common Labels

| Label             | Use Case                                           |
| ----------------- | -------------------------------------------------- |
| `TRACKING`        | Meta/planning issues that track multiple sub-tasks |
| `NEWS`            | Community announcements and updates                |
| `ext-issue`       | External user requests (tier upgrades, etc.)       |
| `app:review`      | New project submission (under review)              |
| `app:info-needed` | Submission awaiting user response