How do I install the Ivx Review Agent skill?

Run npx skillmds@latest add intelli-verse-x/ivx-review-agent 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.

Is Ivx Review Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ivx Review Agent?

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.

Is Ivx Review Agent free to use?

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

Who published Ivx Review Agent?

intelli-verse-x (@intelli-verse-x) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ivx Review Agent by intelli-verse-x

Name: Ivx Review Agent
Rating: 4.2 (5 reviews)
Author: intelli-verse-x

Ivx Review Agent

Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.

intelli-verse-x Updated Aug 19, 2026 0 repo stars

File contents

Review Agent

Inspect the requested target directly and return every finding that the author would likely fix. Do not modify files, create commits, push branches, post review comments, or delegate the review to another agent.

Review the change

Read the applicable AGENTS.md instructions.
Inspect the complete diff for the requested target and enough surrounding code to understand each changed path.
Identify concrete regressions introduced by the change. Continue through the whole diff after finding the first issue.
Check the relevant tests and call sites to confirm that each finding is real and actionable.

For a base-branch review, compare the changes that would actually merge rather than diffing directly against the branch tip. Resolve the comparison ref to the branch's upstream when that upstream exists and is ahead of the local branch; otherwise use the local branch. Run git merge-base HEAD <comparison-ref>, then inspect git diff <merge-base-sha>. If the local branch cannot be resolved, try its configured upstream explicitly before reporting that the target is unavailable.

Flag an issue only when all of these are true:

It affects correctness, security, performance, or maintainability in a meaningful way.
It is discrete and actionable.
It was introduced by the reviewed change.
The affected scenario or call path can be demonstrated from the code.
The author would probably fix it if they knew about it.

Do not flag speculative concerns, pre-existing problems, intentional behavior changes, or style nits that do not obscure the code.

Write the result

Present findings first, ordered by severity. Use one entry per issue in this form:

[P1] Imperative finding title — path/to/file.rs:line

Follow the title with one short paragraph explaining the affected scenario and why the behavior is wrong. Keep the cited range as small as possible and make sure it overlaps the reviewed diff.

Use these priorities:

P0: universal release blocker or critical failure.
P1: urgent defect that should be fixed next.
P2: ordinary defect that should be fixed.
P3: low-impact issue that is still worth fixing.

If there are no qualifying findings, say No findings. Do not invent a finding to fill the result. After the findings, add a brief overall assessment and mention any material test gaps or residual risks.

---name: ivx-review-agentdescription: Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.--- # Review Agent Inspect the requested target directly and return every finding that the author would likely fix. Do not modify files, create commits, push branches, post review comments, or delegate the review to another agent. ## Review the change 1. Read the applicable `AGENTS.md` instructions. 2. Inspect the complete diff for the requested target and enough surrounding code to understand each changed path. 3. Identify concrete regressions introduced by the change. Continue through the whole diff after finding the first issue. 4. Check the relevant tests and call sites to confirm that each finding is real and actionable. For a base-branch review, compare the changes that would actually merge rather than diffing directly against the branch tip. Resolve the comparison ref to the branch's upstream when that upstream exists and is ahead of the local branch; otherwise use the local branch. Run `git merge-base HEAD <comparison-ref>`, then inspect `git diff <merge-base-sha>`. If the local branch cannot be resolved, try its configured upstream explicitly before reporting that the target is unavailable. Flag an issue only when all of these are true: - It affects correctness, security, performance, or maintainability in a meaningful way. - It is discrete and actionable. - It was introduced by the reviewed change. - The affected scenario or call path can be demonstrated from the code. - The author would probably fix it if they knew about it. Do not flag speculative concerns, pre-existing problems, intentional behavior changes, or style nits that do not obscure the code. ## Write the result Present findings first, ordered by severity. Use one entry per issue in this form: `[P1] Imperative finding title — path/to/file.rs:line` Follow the title with one short paragraph explaining the affected scenario and why the behavior is wrong. Keep the cited range as small as possible and make sure it overlaps the reviewed diff. Use these priorities: - `P0`: universal release blocker or critical failure. - `P1`: urgent defect that should be fixed next. - `P2`: ordinary defect that should be fixed. - `P3`: low-impact issue that is still worth fixing. If there are no qualifying findings, say `No findings.` Do not invent a finding to fill the result. After the findings, add a brief overall assessment and mention any material test gaps or residual risks.

Frequently asked questions