OpenRuna
Sign in
SKILL.md

name: review-security description: Review code changes with Security Review subagent.

Review Security

Use this skill when the user asks to run /review-security.

Launch exactly one security-review subagent with:

  • readonly: true
  • run_in_background: false unless explicitly asked to run in background
  • description: "Security Review"
  • subagent_type: "security-review"

The review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.

By default, the review subagent infers the repository's actual base branch, such as main, when computing branch changes. In most cases, do not provide Base Branch. Only provide it if you know the current branch or PR should be compared against a specific branch other than the repository's default base branch, such as when you created the current branch from another branch.

Special case: if the user explicitly asks to review a specific PR or branch, make sure that target is checked out before launching the subagent:

  • Examples include github.com/... /review, review {link}, or review {branch-name}.
  • Resolve the provided PR link, PR number, or branch name to the PR head branch or named branch.
  • Check whether the target branch is already the currently checked out local branch. If it is, continue.
  • If a different branch is currently checked out, try to switch to the target branch.
  • If Git refuses to switch because local files would be overwritten, conflicts need resolution, or another checkout blocker occurs, explain the blocker and ask whether the user wants to stash local changes before retrying.
  • Only stash after the user confirms. If the stash succeeds, retry switching to the target branch.
  • Launch the review subagent only after the target branch is checked out locally.

Use this exact prompt shape:

Full Repository Path: <absolute repository path>
Diff: <one of: "branch changes", "uncommitted changes">
Base Branch: <only include this line when reviewing branch changes against a known specific base branch>
Custom Instructions: <only include this line when the user gave specific review instructions>

Default to branch changes, which reviews branch changes against the merge-base with the default/base branch, including committed, staged, and unstaged changes. If the user asks to review only uncommitted, local working tree, dirty, or not-yet-committed changes, use uncommitted changes.

If the review subagent fails before producing findings, inspect the failure text.

  • If the failure is caused by calling the subagent incorrectly, such as a missing Full Repository Path, missing Diff, wrong prompt shape, or wrong subagent type, correct the invocation and retry it once immediately.
  • For any other subagent failure, retry once with the same prompt shape.
  • If the same failure persists after the retry, stop. Briefly tell the user that the review subagent could not complete and include the short error or blocker. Do not keep retrying.

After the subagent finishes, summarize the result:

  • If it reports that no diff was found or the diff is empty, tell the user in one sentence that there was no diff to review.
  • If it found no issues, give a one-line status such as "Security review found 2 findings / Security review found no issues".
  • If it found issues, print a compact markdown table with one row per finding, sorted by severity (highest first), using exactly these columns: Severity, Location (file:line), Finding. Put the file and line in the location column as file:line.

Do not fix findings or rerun review unless the user explicitly asks for that next step.

Overview

review-security: a free, copy-ready skill on OpenRuna. Review code changes with Security Review subagent.

What this skill does

"review-security" is a skill you can copy, adapt, and run with any modern AI assistant. Review code changes with Security Review subagent. OpenRuna cross-links it to related prompts, agents, and tools, which makes assembling a full workflow around it straightforward. Copy it into your assistant of choice and sharpen the result with a couple of follow-up turns.

Use cases

  • Hand "review-security" to a new teammate so their skill output matches your team's quality bar from day one.
  • Use "review-security" when you need a repeatable skill for professional work without rewriting instructions every time.
  • Reach for it during planning or review sessions when you want consistent, AI-assisted structure.
  • Combine it with related tools and prompts in the same OpenRuna category to build an end-to-end workflow.

Example output

Running this skill produces output shaped like the source material below:

# Review Security

Use this skill when the user asks to run `/review-security`.

Launch exactly one `security-review` subagent with:

- `readonly: true`
- `run_in_background: false` unless explicitly asked to run in background
- `description: "Security Review"`
- `subagent_type: "security-review"`

The review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.

By default, the review subagent infers the repository's actual b…

Results vary by model and temperature; treat the first response as a draft and refine it with follow-up prompts.

Tips by platform

Claude

With Claude, drop this skill into Project knowledge so every chat in the project inherits it. Ask Claude to restate the goal first, then run — it catches edge cases early.

ChatGPT

In ChatGPT, start a fresh chat and paste this skill verbatim, then follow up with "apply this to [your context]." Pick a current GPT model for coding or reasoning tasks.

Cursor

In Cursor, lift the key instructions from this skill into .cursorrules or a SKILL.md file, then reference it in Agent mode with @ mentions. Keep the title in a comment so teammates can find it on OpenRuna.

Frequently asked questions

What is "review-security"?
It is a skill listed on OpenRuna — Review code changes with Security Review subagent. You can copy and adapt it for ChatGPT, Claude, Cursor, or any other AI assistant.
Is "review-security" free to use?
Most OpenRuna resources are open or CC0-licensed. Check the license shown on this page before commercial use; premium collections are clearly marked as such.
How do I get the best results from this skill?
Replace any placeholders, add your project context, and ask the model to confirm its assumptions first. Iterate over 2–3 follow-up turns rather than expecting a perfect first response.
Does "review-security" work with both Claude and ChatGPT?
Yes — it is model-agnostic text, so it runs on Claude, ChatGPT, Gemini, and Cursor. The tips on this page cover each of those assistants specifically.
Where can I find resources related to "review-security"?
Scroll to the Related resources section on this page, or open the matching category hub on OpenRuna to find connected prompts, tools, agents, and datasets in the same topic area.

Related resources