roborev:fix

Fix unaddressed code review findings by running Go tests and marking jobs addressed.

330|47|Updated Aug 30, 2020
One-click install
npx skills add https://github.com/harperreed/dotfiles --skill roborev-fix-harperreed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roborev:fix
Source: https://github.com/harperreed/dotfiles/tree/main/.codex/skills/roborev-fix
Command: npx skills add https://github.com/harperreed/dotfiles --skill roborev-fix-harperreed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the grind of revisiting multiple code review comments by automatically discovering unaddressed review findings and applying fixes across all of them in one workflow.

Core Features & Use Cases

  • Bulk discovery: Finds unaddressed review jobs when no job IDs are provided, or operates on a user-specified set of job IDs.
  • Consolidated fixing: Fetches full reviews for all jobs, parses findings, groups them by file, and fixes by severity while handling related findings together.
  • Verification & tracking: Runs the test suite to confirm correctness, then leaves a summary comment and marks each addressed job to prevent repeat work.
  • Use Case: After a batch of reviews lands on a repo, use this to resolve every remaining finding and update each review thread with what changed.

Quick Start

Run roborev:fix with no job IDs to automatically discover and fix all unaddressed reviews, then verify and record the changes.

Frequently Asked Questions about roborev:fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix multiple code review findings in one session?▼

Fix multiple code review findings by discovering unaddressed review jobs, fetching full review data, grouping findings by file, and applying coordinated code changes. This workflow prioritizes issues by severity and minimizes file context switches.

Can I automatically resolve unaddressed code review comments in a Go repository?▼

Automatically resolve unaddressed code review comments in a Go repository by parsing findings with file and line locations, applying fixes, and running go test ./... to confirm correctness. The workflow then comments on and marks each job as addressed.

What is the best way to automate fixing code review threads while maintaining CI readiness?▼

Automate fixing code review threads while maintaining CI readiness by grouping related findings by file, applying severity-based fixes, and running the Go test suite to verify correctness. It leaves a summary comment and marks each job as addressed to prevent repeat work.

Do I need a runnable Go test suite to use automated repair workflows for repository maintenance?▼

A runnable Go test suite is required for automated repair workflows targeting repository maintenance. The fixing process runs go test ./... to confirm correctness before commenting and marking each addressed job to prevent repeat work.

How does bulk discovery work for unresolved code review findings?▼

Bulk discovery for unresolved code review findings works by automatically finding unaddressed review jobs when no job IDs are provided, fetching full reviews for all jobs, and operating on a user-specified set of job IDs if provided.