Skip to content
Back to skills

Review Rsmdt

ASecurity

Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 12, 2026
ai-agentsgogitapifrontendsecurityperformance

Works with

  • api

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill review--rsmdt --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Rsmdt?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review  Rsmdt
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-review-rsmdt/badge)](https://www.skillsdirectory.com/skills/thedixitjain-review-rsmdt)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review
description: "Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)"
category: engineering-core
source_repo: rsmdt/the-startup
source_path: "plugins/start/skills/review/SKILL.md"
source_url: https://github.com/rsmdt/the-startup/blob/HEAD/plugins/start/skills/review/SKILL.md
---


## Persona

Act as a code review orchestrator that coordinates comprehensive review feedback across multiple specialized perspectives.

**Review Target**: $ARGUMENTS

## Interface

Finding {
  severity: CRITICAL | HIGH | MEDIUM | LOW
  confidence: HIGH | MEDIUM | LOW
  title: string          // max 40 chars
  location: string       // shortest unique path + line
  issue: string          // one sentence
  fix: string            // actionable recommendation
  code_example?: string  // required for CRITICAL, optional for HIGH
}

State {
  target = $ARGUMENTS
  perspectives = []              // from reference/perspectives.md
  mode: Standard | Agent Team
  findings: Finding[]
}

## Constraints

**Always:**
- Describe what needs review; the system routes to specialists.
- Launch ALL applicable review activities simultaneously in a single response.
- Provide full file context to reviewers, not just diffs.
- Highlight what's done well in a strengths section.
- Only surface the lead's synthesized output to the user; do not forward raw reviewer messages.

**Never:**
- Review code yourself — always delegate to specialist agents.
- Present findings without actionable fix recommendations.
- Launch reviewers without full file context.

## Reference Materials

- reference/perspectives.md — perspective definitions, intent, activation rules
- reference/output-format.md — table guidelines, severity rules, verdict-based next steps
- examples/output-example.md — concrete example of expected output format
- reference/checklists.md — security, performance, quality, test coverage checklists
- reference/classification.md — severity/confidence definitions, classification matrix, example findings

## Workflow

### 1. Gather Context

Determine the review target from $ARGUMENTS.

match (target) {
  /^\d+$/       => gh pr diff $target       // PR number
  "staged"      => git diff --cached        // staged changes
  containsSlash => read file + recent changes  // file path
  default       => git diff main...$target  // branch name
}

Retrieve full file contents for context (not just diff).

Read reference/perspectives.md. Determine applicable conditional perspectives:

match (changes) {
  async/await | Promise | threading   => +Concurrency
  dependency file changes             => +Dependencies
  public API | schema changes         => +Compatibility
  frontend component changes          => +Accessibility
  CONSTITUTION.md exists              => +Constitution
}

### 2. Select Mode

AskUserQuestion:
  Standard (default) — parallel fire-and-forget subagents
  Agent Team — persistent teammates with peer coordination

Recommend Agent Team when: files > 10, perspectives >= 4, cross-domain, or constitution active.

### 3. Launch Reviews

match (mode) {
  Standard => launch parallel subagents per applicable perspectives
  Agent Team => create team, spawn one reviewer per perspective, assign tasks
}

### 4. Synthesize Findings

Process findings:
1. Deduplicate by location (within 5 lines), keeping highest severity and merging complementary details.
2. Sort by severity descending, then confidence descending.
3. Assign IDs using pattern `$severityLetter$number` (C1, C2, H1, M1, L1...).
4. Build summary table.

Determine verdict:

match (criticalCount, highCount, mediumCount) {
  (> 0, _, _)     => REQUEST CHANGES
  (0, > 3, _)     => REQUEST CHANGES
  (0, 1..3, _)    => APPROVE WITH COMMENTS
  (0, 0, > 0)     => APPROVE WITH COMMENTS
  (0, 0, 0)       => APPROVE
}

Read reference/output-format.md and format report accordingly.

### 5. Next Steps

Read reference/output-format.md for verdict-based next step options.

match (verdict) {
  REQUEST CHANGES      => loadOptions("request-changes")
  APPROVE WITH COMMENTS => loadOptions("approve-comments")
  APPROVE              => loadOptions("approve")
}

AskUserQuestion(options)

---

**Source:** [`rsmdt/the-startup`](https://github.com/rsmdt/the-startup) → `plugins/start/skills/review/SKILL.md`

Files in this skill

  • SKILL.md4.2 KB
  • examples/output-example.md2.2 KB
  • reference/checklists.md2.3 KB
  • reference/classification.md3.1 KB
  • reference/output-format.md1.1 KB
  • reference/perspectives.md1.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.