How do I install the Miro Code Review skill?

Run npx skillmds@latest add tomevault-io/miro-code-review-2 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 Miro Code Review safe to use?

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

Which AI agents work with Miro Code Review?

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 Miro Code Review free to use?

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

Who published Miro Code Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Miro Code Review by tomevault-io — Agent Skill

Name: Miro Code Review
Author: tomevault-io

File contents

Code Review Skill

This skill provides knowledge and patterns for conducting effective code reviews with visual outputs on Miro boards.

Core Concepts

Review Philosophy

Effective code reviews focus on:

Correctness - Does the code do what it's supposed to?
Security - Are there vulnerabilities or data exposures?
Maintainability - Can others understand and modify this code?
Performance - Are there efficiency concerns?
Consistency - Does it follow project conventions?

Visual Review Benefits

Creating visual artifacts helps:

Async collaboration - Reviewers can engage at their own pace
Context preservation - Related docs and diagrams in one place
Discussion tracking - Comments attached to specific items
Knowledge sharing - Junior devs learn from visual explanations

Risk Assessment Framework

Use the references in this skill for detailed risk assessment criteria:

references/risk-assessment.md - File and change risk scoring
references/review-patterns.md - Common review patterns and anti-patterns

Visualization Patterns

When to Use Each Artifact

Artifact	Best For
Table	File lists, structured comparisons, status tracking
Document	Summaries, detailed analysis, checklists
Flowchart	Process flows, decision trees, bug fix context
Class Diagram	Structural changes, refactoring, OOP patterns
Sequence Diagram	API interactions, message flows, integrations
ER Diagram	Database changes, data model updates

Layout Guidelines

┌─────────────────────────────────────────────────────────┐
│                    MIRO BOARD LAYOUT                     │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  x=-2000          x=0              x=2000      x=4000   │
│  ┌─────────┐      ┌─────────┐      ┌─────────┐         │
│  │ Summary │      │  Table  │      │ Diagram │  y=0    │
│  │   Doc   │      │ (files) │      │  (arch) │         │
│  └─────────┘      └─────────┘      └─────────┘         │
│                                                         │
│  ┌─────────┐                       ┌─────────┐         │
│  │ Detail  │                       │ Diagram │  y=1500 │
│  │   Doc   │                       │ (flow)  │         │
│  └─────────┘                       └─────────┘         │
│                                                         │
└─────────────────────────────────────────────────────────┘

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: miro-code-review-2description: Knowledge and patterns for effective code review visualization Use when this capability is needed.---# Code Review SkillThis skill provides knowledge and patterns for conducting effective code reviews with visual outputs on Miro boards.## Core Concepts### Review PhilosophyEffective code reviews focus on:1. **Correctness** - Does the code do what it's supposed to?2. **Security** - Are there vulnerabilities or data exposures?3. **Maintainability** - Can others understand and modify this code?4. **Performance** - Are there efficiency concerns?5. **Consistency** - Does it follow project conventions?### Visual Review BenefitsCreating visual artifacts helps:- **Async collaboration** - Reviewers can engage at their own pace- **Context preservation** - Related docs and diagrams in one place- **Discussion tracking** - Comments attached to specific items- **Knowledge sharing** - Junior devs learn from visual explanations## Risk Assessment FrameworkUse the references in this skill for detailed risk assessment criteria:- `references/risk-assessment.md` - File and change risk scoring- `references/review-patterns.md` - Common review patterns and anti-patterns## Visualization Patterns### When to Use Each Artifact| Artifact | Best For ||----------|----------|| **Table** | File lists, structured comparisons, status tracking || **Document** | Summaries, detailed analysis, checklists || **Flowchart** | Process flows, decision trees, bug fix context || **Class Diagram** | Structural changes, refactoring, OOP patterns || **Sequence Diagram** | API interactions, message flows, integrations || **ER Diagram** | Database changes, data model updates |### Layout Guidelines```┌─────────────────────────────────────────────────────────┐│ MIRO BOARD LAYOUT │├─────────────────────────────────────────────────────────┤│ ││ x=-2000 x=0 x=2000 x=4000 ││ ┌─────────┐ ┌─────────┐ ┌─────────┐ ││ │ Summary │ │ Table │ │ Diagram │ y=0 ││ │ Doc │ │ (files) │ │ (arch) │ ││ └─────────┘ └─────────┘ └─────────┘ ││ ││ ┌─────────┐ ┌─────────┐ ││ │ Detail │ │ Diagram │ y=1500 ││ │ Doc │ │ (flow) │ ││ └─────────┘ └─────────┘ ││ │└─────────────────────────────────────────────────────────┘```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/miroapp) — claim your Tome and manage your conversions.

Frequently asked questions

Miro Code Review