Bug-to-file prediction as a triage API
Package a bug-to-file localization model as an API or IDE/CI plugin that, given a bug report or stack trace, predicts which files in a repo need to change. Sell it to engineering teams as a triage accelerator, or bundle it into code review and bug tracker tools (Jira, Linear, GitHub Issues) to auto-suggest owners and files for incoming bugs, cutting time spent hunting through large codebases.
What to build
A CLI/IDE extension for solo developers and small teams that takes a bug report or stack trace and predicts which files in the repo need to change, using a bug-localization model — shippable as a VS Code extension or GitHub Action that comments on issues with suggested files.
Bug triage eats hours hunting through unfamiliar codebases; a model trained on real-world fix history can shortcut that search and turn a bug report straight into a ranked file list.
Demand
Solo devs and small teams maintaining large or inherited codebases want faster triage, and AI coding assistants have primed users to expect this kind of automated code navigation.
- Hacker NewsAnnouncement
Show HN: Wn – find the files a bug touches, trained on 1.1M real fixes — 6 points, 0 comments on HN.
Stack
- OpenAI/Claude API for report parsing
- Sentence embeddings (e.g. sentence-transformers)
- GitHub Issues/Actions API
- VS Code Extension API
- Postgres or SQLite for repo file index
- Supabase
Solo + AI difficulty
The hard part is the ML model itself (already built by the original project, so a builder could fork/wrap it rather than retrain); the easy part is wiring a GitHub Action or VS Code extension around an existing API. Time-to-MVP is roughly 1-2 weeks if reusing the open-source model, versus months if training a proprietary one.
- Entry threshold
- Model training on 1.1M fixes is already done by the original author, so a builder would need to wrap it as a hosted API, VS Code extension, or GitHub App with repo indexing; a usable MVP wrapper is a few weeks of work but real integration into CI or issue trackers to be reliable takes more iteration.
- Window
- 3-6 months
Where to find first users
- Show HN follow-up post
- GitHub Marketplace listing for the Action
- r/programming and r/devops
- Indie hacker / build-in-public communities
Competitors
- Wn (where-next, the original open-source project)
Counter-signals & risks
Bug localization accuracy trained on public/open-source fix datasets may not generalize well to proprietary, large, or monorepo codebases with different architectures and conventions
Existing bug tracker and IDE ecosystems (e.g., GitHub Copilot, Sentry, Jira integrations) may add similar file-prediction features natively, reducing the market for a standalone tool
Show HN traction and a novel model do not guarantee enterprise adoption, since engineering teams may be cautious about trusting automated triage suggestions without strong precision/recall guarantees
Original title: Show HN: Wn – find the files a bug touches, trained on 1.1M real fixes
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