Star on GitHub
Star on GitHub

PRSense Roadmap: The System of Record for Engineering Intelligence

PRSense started as a tool to find duplicate Pull Requests.

With v1.1.0, it became Repository Memory—indexing PRs, files, and authors.

With v2.0.0, it became Multi-Provider Infrastructure—supporting GitHub, GitLab, and Bitbucket with real-time webhook processing, BYOK, and organizational API management.

With v2.1.0, it introduced Semantic Code Intelligence—parsing ASTs and scoring Code Health.

With v2.2.0, it became a Live Intelligence & Refactor Hub—integrating actual LLMs to analyze code style and generate safe PRs to fix technical debt.

For v3.0, our vision is the Self-Evolving Codebase Engine — a repository that improves itself automatically.

Phase 1: Code Intelligence (v2.1.0) (Shipped)

  • AST Parsing: Parse TypeScript/JavaScript code using Tree-sitter to understand structure, not just text.
  • Code Health Score: Dashboard page showing repository health metrics — dead code, duplicate logic blocks, circular imports, complexity hotspots.
  • Style Learning: Analyze naming conventions, architecture patterns, error handling to build a “Codebase Style Profile” per repository.

Shipped in v2.0.0 (Shipped)

  • Full GitLab & Bitbucket Webhook Processing — Real MR/PR duplicate detection across all three platforms.
  • Cross-Repo Radar — Detect duplicates across an entire org’s repositories.
  • Webhook Alerts — Slack/Discord notifications for detected duplicates.
  • BYOK (Bring Your Own Key) — Users supply their own OpenAI keys.
  • API Key Management — Organization-scoped key creation, listing, and revocation.

The v3.0 Vision: Self-Evolving Codebase Engine

Phase 3: Full Autonomy (v3.0.0)

  • Learning Loop: If user merges a suggested PR → boost confidence. If user closes → learn to avoid.
  • Complex Refactors: Rename variables, replace algorithms, restructure modules.
  • Scheduled Scans: Weekly, per-commit, or on-demand codebase analysis.

The Future is Open

We are building this in the open because developers deserve tools that understand them. If you want to help us build the “Second Brain” for engineering teams, check out CONTRIBUTING.md.