PR screening bot for AI-generated contributions
Build a GitHub App or CI bot for open-source maintainers that scans incoming pull requests for signs of AI-generated code (boilerplate patterns, hallucinated APIs, inconsistent style, missing tests, template-like PR descriptions) and auto-labels or flags them for review, helping projects enforce new no-AI or disclose-AI-usage contribution policies. Secondary market: companies with internal contribution guidelines wanting the same triage on pull requests.
What to build
A GitHub App / CI bot for open-source maintainers that scans incoming pull requests for signs of AI-generated code (boilerplate patterns, hallucinated API calls, inconsistent style, missing tests, template-like PR descriptions) and auto-labels or flags them so maintainers can enforce no-AI or disclose-AI-usage contribution policies.
Open-source projects are starting to adopt formal bans or disclosure rules on AI-generated pull requests, creating demand for a bot that automatically flags likely AI-authored contributions for maintainer review.
Demand
OSS maintainers adopting AI-contribution policies, and companies with internal contribution guidelines, both need a lightweight way to triage incoming PRs without manually eyeballing every diff for AI tells.
- Hacker News (osssaysno.com)Engagement
Post on OSS projects banning AI-generated contributions reached 62 points and 106 comments, indicating high engagement with the topic.
Stack
- GitHub Apps API
- GitHub Actions / Probot
- OpenAI or Anthropic API (for classification heuristics)
- Node.js or Python backend
- Postgres (for flagged-PR history)
- Vercel or Fly.io for hosting
Solo + AI difficulty
MVP (webhook listener, basic heuristics, PR label/comment) is a few days with AI assist. Hard part is reducing false positives as AI coding tools get better at mimicking human style, and handling GitHub App review/installation flow. Time-to-MVP: roughly 1-2 weeks.
- Entry threshold
- Low barrier - can be shipped as a GitHub App using the GitHub API plus LLM calls for classification, hosted on serverless infra; the main effort is tuning detection to avoid false positives, realistic in 1-3 weeks for one builder.
- Window
- 6-12 months
Where to find first users
- GitHub Marketplace listing
- r/opensource and r/programming
- Hacker News launch post
- Direct outreach to maintainers of large repos with CONTRIBUTING.md AI policies
Counter-signals & risks
Detection heuristics (style inconsistency, boilerplate, hallucinated APIs) are prone to false positives/negatives as AI coding tools improve and better mimic human style.
No historical match for this signal suggests it may be an isolated or early-stage trend rather than a broad, sustained movement across OSS projects.
Maintainers may resist adding another automated gatekeeping layer to already strained PR review workflows, or prefer social/policy enforcement over tooling.
Original title: OSS projects banning AI-generated contributions
Related signals
- Developer tools#4
MCP Connector Library for AI Coding Agents
Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.
Demand7/10est.Buildability7/10est.Competition7/10est.via Product Hunt22 competitors - Developer tools#7
Plan State Persistence Layer for Claude Code Re-Runs
Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.
Demand6/10est.Buildability8/10est.Competition8/10est.via Product Hunt11 competitor - Developer tools#8
Developer Context Save and Restore Tool as Micro-SaaS
Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.
Demand1/10measuredBuildability7/10est.Competition6/10est.via Hacker News33 competitors