The issue-maker skill for Claude streamlines GitHub project management by automating the creation of issues according to specific team standards. It helps developers and project managers maintain consistency in task tracking, feature planning, and team assignments using the GitHub CLI, ensuring every issue is properly labeled, assigned, and formatted for maximum clarity and team alignment.

When should I use issue-maker?

issue-maker is useful in the following scenarios: • Feature Planning: Converting brainstormed feature lists or technical requirements into structured GitHub issues with appropriate labels and domain-specific assignees. • Project Milestone Tracking: Creating comprehensive 'Tracking Issues' that aggregate multiple sub-tasks to monitor the progress of complex development cycles. • Workflow Standardization: Enforcing team-specific style guides and conventions, such as mandatory emoji usage and concise bullet-point formatting, to maintain repository hygiene. • Rapid Request Processing: Efficiently converting community feedback, external user requests, or tier upgrade applications into actionable internal tickets using predefined templates.

name	issue-maker
description	Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.

Issue-Maker

Turn any user request into GitHub issues following team conventions.

Hard Rules

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

Workflow

1. Research First

Before creating any issues:

# 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

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
`app:approved`	Project approved and merged
`app:denied`	Submission rejected

Issue Templates

Standard Issue (max 3 bullets)

-   Adds X to Y
-   Fix Z by doing W
-   Related: #1234

Tracking Issue (more detailed)

## Overview

Brief description

## Tasks

-   [ ] Task 1
-   [ ] Task 2
-   [ ] Task 3

## Related

-   #issue1
-   #issue2

Tier Upgrade Request

-   Upgrade @USERNAME to TIER tier
-   Qualification: [reason]
-   Related: #original_request_issue

Style Guide

Short, sharp, no fluff
Smart emojis (not overdone)
Bullet points over paragraphs
Reference @eulervoid's style: repo:pollinations/pollinations author:eulervoid

Example Commands

Create simple issue:

gh issue create --repo pollinations/pollinations \
  --title "🔧 Fix caching header for image service" \
  --body "- Update cache-control header
- Add proper ETag support
- Related: #4100" \
  --assignee voodoohop

Create tracking issue:

gh issue create --repo pollinations/pollinations \
  --title "📋 TRACKING: Q4 Model Updates" \
  --body "## Overview
Track all model-related updates for Q4

## Tasks
- [ ] Add Claude Sonnet 4.5
- [ ] Update pricing tiers
- [ ] Deprecate old models" \
  --label "TRACKING" \
  --assignee voodoohop

Comment on issue:

gh issue comment 1234 --repo pollinations/pollinations \
  --body "✅ Done! Merged in #5678"

issue-maker

When & Why to Use This Skill

Use Cases