IssueTriage - AI GitHub Issue Auto-Prioritizer for Maintainers

One-click GitHub integration that learns your project's priority patterns and auto-labels incoming issues by severity, duplicates, and required effort. Saves maintainers 8+ hours per week triaging.

𝕏 Post Reddit HN

Difficulty

intermediate

What is it?

Open source maintainers and small dev teams drown in incoming GitHub issues. Every issue needs manual review to determine if it's a bug, feature request, duplicate, or spam. This process takes 15-30 minutes per issue, scaling from annoying to impossible around 50+ issues per week. IssueTriage connects to your GitHub repo, analyzes your historical issue labels and discussions, and uses Claude to auto-assign priority labels (P0/P1/P2), mark duplicates, estimate effort (1h/1d/1w), and surface similar issues. Maintainers click once per week to confirm or adjust. For teams managing 100+ issues monthly, this eliminates 60-70% of triage overhead and ensures high-signal issues never get buried. Why 100% buildable right now: GitHub API v3 for issue webhooks is stable and battle-tested. Claude's text understanding has shipped in production at Anthropic and across thousands of apps. Supabase handles webhook ingestion and storage. No custom ML training needed—Claude's few-shot learning from your own label history is sufficient.

Why now?

GitHub released v4 GraphQL API improvements in early 2026, and Claude's API now supports batch processing which reduces costs 50% for high-volume repos. Open source maintainer burnout is at peak complaint on Hacker News and Twitter/X.

▸Auto-label issues by severity and effort (Implementation: Claude analyzes issue text + historical labels, returns structured JSON)
▸Duplicate detection and linking (Implementation: Claude embeddings comparison, surface top 3 similar closed issues)
▸Smart webhook ingestion and batching (Implementation: Supabase real-time, queue 10 issues before Claude call)
▸Maintainer approval dashboard with one-click confirm/adjust (Implementation: Next.js form, Stripe webhook sync on approve)

Target Audience

Open source maintainers and small dev teams managing 100+ issues/month. ~30,000 maintainers in top 500 npm packages alone.

Example Use Case

Maya maintains a 2,000-star open source CLI tool and receives 40-60 issues per week. Without IssueTriage, she spends 6 hours triaging. With it, she spends 30 minutes reviewing AI suggestions, saving her 5.5 hours per week. She upgrades to Pro ($9/month) and reinvests the saved time into features, improving project velocity by 40%.

User Stories

▸As a busy open source maintainer with 100+ monthly issues, I want AI to auto-label issues by priority and effort, so that I spend 5 hours less per week on triage and more time coding.
▸As a project lead, I want to see a dashboard of pending issue labels before they're published, so that I can enforce project standards and adjust rules over time.
▸As a GitHub user with limited bandwidth, I want duplicate issues auto-detected and linked, so that the community doesn't fragment into split discussions.

Acceptance Criteria

GitHub OAuth: done when user can install app via GitHub Marketplace and authorize repo access. Issue webhook: done when new issue triggers Claude API call within 10 seconds and label appears in dashboard. Maintainer approval: done when clicking approve posts label back to GitHub issue immediately. Stripe integration: done when user clicks upgrade, pays, and Pro features unlock without manual activation.

Is it worth building?

$9/month × 200 users (free to paid conversion 12% of 1,667 beta signups) = $1,800 MRR at month 2. $49/month × 150 power users = $7,350 MRR at month 4.

Unit Economics

CAC: $5 (ProductHunt + Reddit organic reach). LTV: $45 (12 months at $3.75/month blended tier price). Payback: 3 months. Gross margin: 70% (after API costs).

Business Model

SaaS subscription with free tier (5 issues/week).

Monetization Path

Free tier: 5 issues/week, basic labeling. Pro: $9/month, unlimited issues, duplicate detection. Enterprise: $99/month, team dashboard, custom rules, API access.

Revenue Timeline

First dollar: week 2 (via ProductHunt badge redirect). $1k MRR: month 2. $5k MRR: month 5. $10k MRR: month 9.

Estimated Monthly Cost

Claude API: $60 (1,000 issues at $0.06/issue estimate). Vercel: $20. Supabase: $25. GitHub API: free. Stripe fees: ~$15 at $1.8k MRR. Total: ~$120/month at launch.

Profit Potential

Full-time viable at $3k–$12k MRR.

Scalability

High — can expand to GitLab, Gitea, Jira, Linear, and sell as Team workspace product for enterprise.

Success Metrics

Week 2: 100 beta signups (ProductHunt launch). Week 3: 20 paid trials. Month 2: 45% free-to-paid conversion. Month 3: 90%+ label accuracy (maintainer feedback).

Launch & Validation Plan

Survey 40 maintainers on GitHub discussions in top 200 npm packages. Build landing page with specific pain metrics. Recruit 10 active repo maintainers for beta (cold outreach via GitHub issues 'help wanted'). Validate that 80% of suggested labels match maintainer intent before launch.

Customer Acquisition Strategy

First customer: Post on r/golang, r/rust, r/Python offering free year for early adopter feedback (target maintainers of 1k+ star repos). Then: ProductHunt (target dev tools category), GitHub trending discussion threads, Tweet thread with specific npm package examples, dev.to article on issue management tooling.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): GitHub webhook ingestion, Claude triage, approval dashboard, Stripe basic subscription. V2 (month 2): duplicate detection, custom label rules, email digest of weekly suggestions. V3 (month 4): GitLab support, team workspace, API endpoint for external tools.

Milestone Plan

Phase 1 (Week 1-2): GitHub OAuth + webhook handler + Claude triage function. Done when test issue triggers label suggestion. Phase 2 (Week 3-4): approval dashboard + Stripe checkout page. Done when beta user can pay and see Pro features. Phase 3 (Month 2): duplicate detection + email notifications. Done when 5 beta maintainers confirm 90% label accuracy.

How do you build it?

Tech Stack

Next.js, GitHub API v3, Claude API, Supabase, Stripe — build backend with Cursor, frontend with Lovable, real-time sync with v0.

Time to Ship

3 weeks

Required Skills

GitHub API integration, Claude API chaining, webhook handling in Next.js, Stripe billing.

Resources

GitHub API docs, Anthropic Claude API docs, Supabase webhooks guide, Stripe integration tutorial.

MVP Scope

GitHub OAuth page (v0), issue webhook receiver (Cursor backend), Claude triage function (Cursor), approval dashboard (Lovable), Stripe payment link (no subscription logic yet). Core files: /pages/api/github/webhook.ts, /pages/api/claude/triage.ts, /components/IssueCard.tsx, /pages/dashboard.tsx.

Core User Journey

Install GitHub app -> connect repo -> receive first auto-labeled issue in 2 minutes -> review dashboard -> approve 80% of labels -> upgrade to Pro within 7 days.

Architecture Pattern

GitHub webhook -> Supabase ingest queue -> Claude API call with repo context -> label JSON stored in Postgres -> dashboard polls for updates -> maintainer approves -> label posted back to GitHub API.

Data Model

Repository has many Issues. Issue has many SuggestedLabels. SuggestedLabel belongs to one Repository. User has many Repositories via OAuth. Approval belongs to one Issue and one User.

Integration Points

GitHub API for webhooks and label posting, Claude API for NLP triage, Supabase for webhook queue and label storage, Stripe for subscription billing, Resend for email notifications.

V1 Scope Boundaries

V1 excludes: team workspace collaboration, GitLab/Gitea support, custom rule engine, CLI tool, mobile app, white-label.

Success Definition

A maintainer with 100+ monthly issues installs the app, uses it for 4 weeks straight, and renews subscription without founder outreach.

Challenges

GitHub rate limiting (60 requests/hour unauthenticated). Requires OAuth token refresh logic. Claude API cost scaling with large repos.

Avoid These Pitfalls

Do not over-engineer custom ML model training on day one—Claude handles few-shot learning. Do not build team collaboration before single-user value is proven. Do not sync labels bidirectionally without idempotency logic (causes conflicts).

Security Requirements

Auth: GitHub OAuth token stored encrypted in Supabase. RLS enabled on all user tables. Rate limiting: 100 req/min per IP. Input validation: sanitize all GitHub webhook payloads. GDPR: no EU issue content stored without explicit consent—store only label suggestions and hashes.

Infrastructure Plan

Hosting: Vercel (frontend + API routes). Database: Supabase Postgres (repositories, issues, labels, users). Storage: Supabase Storage for user preference backups. CI/CD: GitHub Actions on push to main. Environments: dev (local Supabase), staging (Vercel preview), prod (Vercel main). Monitoring: Sentry for errors, Vercel Analytics for traffic, custom webhook failure alerts.

Performance Targets

Expected load at launch: 500 DAU, 2,000 webhook deliveries/day. Webhook processing target: under 5 seconds per issue. Dashboard load target: under 1.5s. Caching: Redis for repo context (label history), CDN for static assets.

Go-Live Checklist

☐Security audit: GitHub OAuth token encryption verified
☐Payment flow: test Stripe checkout with dummy card
☐Error tracking: Sentry configured and test error posted
☐Monitoring: custom dashboard for webhook failures and Claude API latency
☐Custom domain: IssueTriage.dev registered and SSL set
☐Privacy policy: GDPR-compliant, published
☐Terms: drafted and reviewed
☐Beta users: 5+ maintainers signed off
☐Rollback: documented revert to manual label posting
☐Launch: ProductHunt post with example repos and Before/After time savings.

How to build it, step by step

1. Create Next.js app with npx create-next-app. 2. Set up Supabase project and create tables (repositories, issues, suggested_labels, users). 3. Register GitHub OAuth app and create /pages/api/auth/github.ts callback. 4. Build /pages/api/github/webhook.ts to receive issue events and insert into queue. 5. Create /lib/claudeClient.ts with issue triage prompt. 6. Build /pages/dashboard.tsx with Supabase real-time subscription. 7. Add Stripe integration with /pages/api/stripe/checkout.ts. 8. Create /components/IssueCard.tsx to display and approve suggestions. 9. Test webhook flow end-to-end with GitHub sandbox. 10. Deploy to Vercel with environment variables.

Generated

March 23, 2026

Model

claude-haiku-4-5-20251001

← Back to All Ideas