How do I install the Rvm skill?

Run npx skillmds@latest add evanoman/rvm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rvm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

EvanOman (@evanoman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rvm by evanoman — Agent Skill

Name: Rvm
Author: EvanOman

File contents

Review-Merge Workflow (RVM)

Complete code review workflow: review changes, address any issues found, then push and merge.

Workflow Steps

Step 1: Code Review

Spawn a sub-agent to perform code review using the same rubric as /review:

Review Rubric:

Category	Severity	Checks
Correctness	Critical	Logic errors, unhandled edge cases, race conditions, resource leaks
Security	Critical	Input validation, injection vulnerabilities, hardcoded secrets
Error Handling	High	Uncaught exceptions, error message leaks, missing cleanup
Code Quality	Medium	Long functions (>50 lines), deep nesting, duplication, poor naming, missing types
Testing	Medium	Missing tests, untested edge cases, flaky tests
Documentation	Low	Missing docstrings, outdated comments

The sub-agent should return issues categorized by severity with file:line references.

Step 2: Address Review Findings

For each issue found:

Critical/High issues: Must be fixed before proceeding
Medium issues: Fix if straightforward, otherwise note as future improvement
Low issues: Fix only if trivial, otherwise skip

After addressing issues:

Run tests to verify fixes don't break anything
Run linter/formatter if available

Step 3: Commit Fixes (if any)

If changes were made to address review feedback:

git add -A
git commit -m "Address code review feedback

- [List of fixes made]

Co-Authored-By: Claude <noreply@anthropic.com>"

Step 4: Push

Push the branch to remote:

git push

Step 5: Merge

Merge the PR:

gh pr merge --squash --delete-branch

If merge fails due to CI, wait and retry or report the issue.

Output Format

Report progress through each step:

## RVM: Review-Merge Workflow

### Review Phase
[Review findings from sub-agent]

### Fixes Applied
- [x] Fixed [issue] in file:line
- [x] Fixed [issue] in file:line
- [ ] Skipped [issue] - [reason]

### Verification
- Tests: PASS/FAIL
- Lint: PASS/FAIL

### Push & Merge
- Pushed: [commit hash]
- PR merged: [PR URL]

Error Handling

If critical issues cannot be fixed automatically, stop and report
If tests fail after fixes, stop and report
If merge fails, report the reason (CI failure, conflicts, etc.)

---name: rvmdescription: Review code, address feedback, push, and merge (Review-Merge workflow). Use when the user wants to review, fix, and ship a branch in one go.---# Review-Merge Workflow (RVM)Complete code review workflow: review changes, address any issues found, then push and merge.## Workflow Steps### Step 1: Code ReviewSpawn a sub-agent to perform code review using the same rubric as `/review`:**Review Rubric:**| Category | Severity | Checks ||----------|----------|--------|| Correctness | Critical | Logic errors, unhandled edge cases, race conditions, resource leaks || Security | Critical | Input validation, injection vulnerabilities, hardcoded secrets || Error Handling | High | Uncaught exceptions, error message leaks, missing cleanup || Code Quality | Medium | Long functions (>50 lines), deep nesting, duplication, poor naming, missing types || Testing | Medium | Missing tests, untested edge cases, flaky tests || Documentation | Low | Missing docstrings, outdated comments |The sub-agent should return issues categorized by severity with file:line references.### Step 2: Address Review FindingsFor each issue found:1. **Critical/High issues**: Must be fixed before proceeding2. **Medium issues**: Fix if straightforward, otherwise note as future improvement3. **Low issues**: Fix only if trivial, otherwise skipAfter addressing issues:- Run tests to verify fixes don't break anything- Run linter/formatter if available### Step 3: Commit Fixes (if any)If changes were made to address review feedback:```bashgit add -Agit commit -m "Address code review feedback- [List of fixes made]Co-Authored-By: Claude <noreply@anthropic.com>"```### Step 4: PushPush the branch to remote:```bashgit push```### Step 5: MergeMerge the PR:```bashgh pr merge --squash --delete-branch```If merge fails due to CI, wait and retry or report the issue.## Output FormatReport progress through each step:```## RVM: Review-Merge Workflow### Review Phase[Review findings from sub-agent]### Fixes Applied- [x] Fixed [issue] in file:line- [x] Fixed [issue] in file:line- [ ] Skipped [issue] - [reason]### Verification- Tests: PASS/FAIL- Lint: PASS/FAIL### Push & Merge- Pushed: [commit hash]- PR merged: [PR URL]```## Error Handling- If critical issues cannot be fixed automatically, stop and report- If tests fail after fixes, stop and report- If merge fails, report the reason (CI failure, conflicts, etc.)

Frequently asked questions

Rvm