Browse Repositories, Pull Requests, and Review Run Details

Explore connected repositories, drill into individual PRs, and inspect review run results with issue severity, code snippets, and confidence scores.

The Repositories page is your starting point for exploring everything BugViper has reviewed. From here you can browse all connected repos at a glance, drill into a specific repository to see its PR history and analytics, and expand individual review runs to inspect every issue BugViper flagged — complete with severity ratings, code snippets, suggested fixes, and confidence scores.

Repository Overview

The main Repositories page displays all connected repositories in a three-column card grid. Each card gives you a quick snapshot of that repository’s review activity:

• Repo name — the GitHub repository name and owner
• Issues caught — total number of valid issues found across all reviews
• Reviews run — total number of individual review runs completed
• Addressed % — the percentage of caught issues that have been resolved or fixed
• Language — the primary language detected in the repository

Scan the grid to quickly identify repos with low addressed rates or unusually high bug counts, then click a card to dig deeper.

Per-Repo Analytics

Clicking a repository card opens a side panel with detailed analytics scoped to that repo. The panel includes:

• Addressed Rate — percentage of issues resolved for this repo specifically
• Avg Merge Time — average time from PR open to merge, for this repo
• PRs/Week — average PR velocity for this repo
• Total Reviews — total review runs completed in this repo
• PR list — a scrollable list of all pull requests that have received a BugViper review, with status, author, and review count for each

Use the per-repo panel when the dashboard metrics flag a problem and you need to find out which PRs are responsible.

Review Run Detail

Expanding any PR in the per-repo panel reveals the individual review runs associated with that PR. Clicking into a run shows the full results, organized into three sections:

1. Walkthrough Summary

   A high-level narrative describing what the PR does, the files changed, and the overall risk profile BugViper assessed. This gives reviewers immediate context before they read the issue list.

2. Positive Findings

   A list of things BugViper found well-implemented in the PR — good use of error handling, well-structured tests, clear naming, and so on. Positive findings are surfaced to reinforce good patterns, not just flag problems.

3. Issues List

   A detailed list of every problem BugViper identified in the run. Each issue includes:

   • Severity badge — visual indicator of how serious the issue is
   • Code snippet — the exact lines of code where the issue was found
   • Impact explanation — a plain-English description of what could go wrong if the issue isn’t addressed
   • Suggested fix — BugViper’s recommended code change or approach to resolve the issue
   • Confidence score — how confident BugViper is in the finding, expressed as a percentage
   • Resolution status — whether the issue is open, resolved, or marked as addressed

Issue Severity Levels

Every issue BugViper flags is assigned one of four severity levels. Use these to prioritize which issues to address first.

Severity	Color	Meaning
critical	Red	Security vulnerability or data loss risk — address before merging
high	Orange	Significant bug or breaking change that will likely cause a failure in production
medium	Yellow	Logic error or performance issue that should be fixed but may not block the merge
low	Blue	Minor issue or code smell — worth cleaning up but low urgency

Only high-confidence issues are posted as inline comments on the GitHub pull request. Lower-confidence findings and issues outside the PR diff appear exclusively in the BugViper dashboard and do not create noise in the PR thread.