roborevaddress
Address findings from a roborev code review by fetching the review and making necessary code changes
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
roborev:address
Fetch a code review and fix its findings.
Usage
/roborev:address <job_id>
Instructions
When the user invokes /roborev:address <job_id>:
1. Fetch the review
Execute:
roborev show --job <job_id>
2. Check the verdict
- If Pass: Inform the user no action is needed
- If Fail: Continue to address the findings
3. Fix the findings
Parse the findings from the output (severity, file paths, line numbers), then:
- Read the relevant files
- Fix issues by priority (high severity first)
- Run tests if the project has them
4. Complete the workflow
After fixing, record what was done by executing:
roborev comment --job <job_id> "<summary of changes>"
This records your comment in roborev so the review shows it was addressed.
Then ask the user if they want to commit the changes.
Example
User: /roborev:address 1019
Agent:
- Executes
roborev show --job 1019 - Sees verdict is Fail with 2 findings
- Reads files, fixes the issues, runs tests
- Executes
roborev comment --job 1019 "Fixed null check in foo.go and added error handling in bar.go" - Asks: "I've addressed both findings and recorded a comment. Tests pass. Would you like me to commit these changes?"
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-02-04
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!