code-review
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
More from miroapp/miro-ai
miro-mcp
>-
235miro-platform
>-
82documentation-structure
Documentation architecture for this repository. Use when creating, updating, or reviewing README.md, CONTRIBUTING.md, or docs/ files. Covers separation of concerns, vendor documentation standards, cross-references, and validation.
76miro-code-review
Use when the user wants to create a visual code review on a Miro board from a pull/merge request (GitHub, GitLab, or any forge), local uncommitted changes, or a branch comparison — produces a file-changes table, summary/architecture/security docs, and architecture diagrams, then links them back from the PR/MR.
69miro-spec-guide
>-
49miro-diagram
Use when the user wants to create a diagram (flowchart, mindmap, UML class, UML sequence, entity-relationship) on a Miro board from a natural-language description or Mermaid/PlantUML notation.
14