Issues
Issues are the individual findings produced by code review sessions. VibeRails gives you powerful tools to filter, tag, batch-edit, and export issues so you can prioritise what matters and act on it quickly.
Issue Table
The Issues screen presents every finding across all review sessions for a project. Each row shows the issue title, the file and line number where it was found, its severity, category, triage status, and any tags you have applied.
Click any row to open the issue detail panel, which shows the full description, code snippet with syntax highlighting, and the AI model's explanation of the problem.
Severity Badges
Every issue is assigned a severity level by the AI model. Severity badges use colour coding for quick visual scanning:
- Critical — red badge. Bugs that will cause crashes, data loss, or security vulnerabilities.
- High — orange badge. Significant problems that should be addressed before shipping.
- Medium — yellow badge. Code quality issues and potential edge cases.
- Low — blue badge. Style suggestions, minor improvements, and informational notes.
Categories
In addition to severity, each issue is classified into a category that describes the type of problem. Common categories include Security, Performance, Logic Error, Error Handling, Type Safety, and Code Style. See the Issue Categories reference for the full list.
Filtering
The filter panel sits above the issue table and lets you narrow results by any combination of:
- Severity — toggle one or more severity levels.
- Category — select one or more issue categories.
- Status — filter by triage status (pending, approved, rejected, deferred).
- Tag — filter by user-applied tags.
- File — type a path or glob to narrow issues to specific files.
- Session — show issues from a particular review session only.
Tagging
Tags let you organise issues with your own labels. Click the tag icon on any issue row to open the inline tag editor. Type a new tag name and press Enter to create it, or select from existing tags in the dropdown.
Tags are shared across all sessions in a project, making them useful for cross-cutting concerns like "needs-discussion", "tech-debt", or sprint-specific labels.
Batch Actions
Select multiple issues using the checkboxes and a batch toolbar appears above the table. Batch actions include:
- Set Status — mark all selected issues as approved, rejected, or deferred.
- Add Tag — apply a tag to all selected issues at once.
- Send to Fix — create a new Fix Session with the selected issues.
- Export — export the selected issues to a file.
Export
VibeRails supports exporting issues in multiple formats. Click the Export button in the toolbar (or from the batch toolbar for a subset) to open the export dropdown:
- CSV — tabular format suitable for spreadsheets and data analysis.
- JSON — structured data for integration with other tools.
- Markdown — formatted report suitable for pull requests and documentation.
Exported files respect your current filters, so you only get the issues you care about. See Export Formats for detailed schema documentation.