Run any Skill in Manus with one click

code-review-artifacts

Stars1

Forks0

UpdatedMay 12, 2026 at 12:20

Create code-review comprehension artifacts (diff briefs, ASCII flow maps, architecture x-rays). Use when the user asks "show me the flow", "what changed", "walk me through this", "xray", "show me the flows", "what does this codebase do", or wants to understand code before approving, merging, or refactoring. Inputs - branch or commit range, scope (file/function/route/CLI command/whole codebase), and a comparison base. Do not use when the user wants approval (this is comprehension, not approval), is doing functional/security/lint review (separate skills), wants a refactor (rewrite request, not review), or is reading already-shipped code that is unchanged. Produces a diff brief OR ASCII flow map OR architecture x-ray, each prefixed with an explicit "Inspected / Not inspected" scope statement. Escalate if scope is unclear, comparison base cannot be determined, or the codebase is too large for a single artifact (recommend a scoped sub-run).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Naoray

Naoray/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

9 files

SKILL.md

readonly

name

code-review-artifacts

description

Code Review Artifacts

Create review artifacts that help a human build a correct mental model before approval. This skill is about comprehension and risk triage, not approval.

Evidence tier: P (practitioner-backed) Basis: program comprehension research (mental-model construction during code reading), change-impact analysis, code review risk triage. Predecessors: flow-review (mode → flow-map) and xray (mode → x-ray) in this registry. Source IDs: program-comprehension literature (Sillito et al. on developer questions during code review), Google/Microsoft modern code review studies, Naoray internal flow-review + xray skills (now consolidated here). Reviewed: 2026-05-12

Context Budget

Read only:

This file.
workflows/preflight.md.
One mode workflow.
One principle file when the selected workflow asks for it.

Do not load every file in this skill. evals/ is not runtime context.

Route

Read this file. Then read exactly one of:

workflows/diff-brief.md — summarize a branch's changes by purpose, list review risks (high/medium/low), suggest a next artifact.
workflows/flow-map.md — trace changed logic and render ASCII runtime paths with [NEW]/[MOD]/[REMOVED] markers.
workflows/xray.md — discover entry points, scope flows, render diagrams, evaluate for dead ends, missing error paths, wrong-direction coupling.

Heuristics:

"what changed", "summarize this PR" → Diff brief.
"show me the flow", "how does this run" → Flow map.
"how does this codebase work", "xray", "architecture review" → X-ray.

Required First Step

Always read workflows/preflight.md before the selected workflow.

Output Rule

Every output MUST state what was inspected and what was not inspected — because reviewers need to know the artifact's scope gap to make an informed approval decision; an unscoped artifact reads as authoritative when it isn't.

More from this repository

same repository

orchestrator-mode

Naoray/skills

Use when the user says `/orchestrator-mode`, asks you to coordinate agents, or gives large multi-phase work needing parallel delegation, reviews, PRs, scratchpads, or handoffs. Inputs - project goal, repo context, Solo agents/processes, branch/worktree constraints, locked user decisions. Do not use for a direct small edit, a normal code review, or single-agent implementation; use focused coding/review skills instead. Produces delegation plan, agent briefs, monitoring protocol, review/merge routing, state hygiene rules. Escalate on unclear scope, product direction, merge authority, destructive cleanup, or tool availability. Delegates are Solo processes: prefer Solo MCP tools, falling back to the `solo` CLI only when MCP is unavailable - never the in-process Task/Agent tool.

2026-06-041

init-rust

Naoray/skills

Use when initializing Rust best-practices rules in a project, the user invokes `/init-rust`, or a new Rust workspace needs convention rules wired up for an agent. Inputs - target project root, an existing or creatable `.claude/rules/` directory, and confirmation the project targets Rust edition 2024 (rules assume 2024 + MSRV 1.85). Do not use when the user wants language-agnostic project init, framework-specific scaffolding (axum, tauri, leptos, etc.), or actual code generation; use those skills or write code directly. Produces `.claude/rules/rust.md` with `paths: "**/*.rs"` frontmatter covering workspace layout, error handling, async/Tokio, CLI (clap), serde, tracing, type system, process supervision, security, testing, naming, tooling, and Edition 2024 changes. Escalate if `.claude/rules/rust.md` already exists with manual edits, the project is not a Rust workspace, or the user targets an edition older than 2024.

2026-05-221

apple-calendar

Naoray/skills

Use when the user asks to list Apple Calendar calendars or events, create/update/delete events, search appointments, or manage recurrence in Calendar.app on macOS. Inputs - calendar name when needed, event UID for read/update/delete, event title, start/end times, location/description/recurrence details for writes. Do not use when the user needs Google/Outlook calendar APIs, cross-platform sync, or general scheduling advice; use a service-specific calendar integration instead. Produces Calendar.app script commands and parsed event/calendar results. Escalate if calendar permissions are missing, the target calendar is read-only, dates are ambiguous, or deleting a recurring event could remove an entire series.

2026-05-221

dev-browser

Naoray/skills

Use when the user asks to navigate a website, click UI, fill forms, take screenshots, scrape visible page data, test a web app, log into a browser session, or automate browser workflows with persistent page state. Inputs - target URL or existing page context, desired browser action, selectors or visible labels when known, credentials only when user explicitly provides them. Do not use when a plain HTTP request, local file edit, or Playwright test suite is the better artifact; use those tools instead. Produces dev-browser CLI commands or sandboxed JavaScript automation steps plus captured results. Escalate if login, payment, destructive actions, CAPTCHA, or sensitive personal data is involved.

2026-05-221

meeting

Naoray/skills

Use when the user says "/meeting [title]", "/meeting end", or wants live meeting note capture from raw fragments during an active meeting. Inputs - meeting title, type, attendees, active meeting state, and real-time notes or end command. Do not use when the user wants post-hoc meeting summarization, a transcript cleanup, or general note-taking outside meeting mode; use summarization or writing skills instead. Produces structured raw notes, action items, decisions, and a shareable meeting summary for review. Escalate if no title is provided, no meeting is active on end, another meeting is already active, or content appears sensitive enough to require confirmation before writing.

2026-05-221

record

Naoray/skills

Use when the user says "/record [message]" or when a meaningful workday event needs a concise timestamped entry in today's running log. Inputs - exact message for manual entries, current date/time, daily note location, and enough context to judge whether an automatic entry is meaningful. Do not use when the user wants a full journal entry, meeting notes, or end-of-day synthesis; use writing, meeting, or evaluate-day instead. Produces one deduplicated timestamped Running Log entry in today's daily note. Escalate if the daily note path cannot be created, the entry would duplicate existing content, or automatic logging would expose sensitive content.

2026-05-221

name

code-review-artifacts

description

Code Review Artifacts

Create review artifacts that help a human build a correct mental model before approval. This skill is about comprehension and risk triage, not approval.

Context Budget

Read only:

This file.
workflows/preflight.md.
One mode workflow.
One principle file when the selected workflow asks for it.

Do not load every file in this skill. evals/ is not runtime context.

Route

Read this file. Then read exactly one of:

workflows/diff-brief.md — summarize a branch's changes by purpose, list review risks (high/medium/low), suggest a next artifact.
workflows/flow-map.md — trace changed logic and render ASCII runtime paths with [NEW]/[MOD]/[REMOVED] markers.
workflows/xray.md — discover entry points, scope flows, render diagrams, evaluate for dead ends, missing error paths, wrong-direction coupling.

Heuristics:

"what changed", "summarize this PR" → Diff brief.
"show me the flow", "how does this run" → Flow map.
"how does this codebase work", "xray", "architecture review" → X-ray.

Required First Step

Always read workflows/preflight.md before the selected workflow.