Perform a Maestro-style code review with findings ordered by severity and concrete file references.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Read `../../references/runtime-guide.md`.
Call `get_skill_content` with resources: ["architecture", "delegation", "code-review"].
Call `get_agent` with agents: ["code-reviewer"].
## Workflow
1. Determine review scope: explicit user-provided paths, staged changes, or last commit diff
2. Delegate to the code-reviewer agent with the diff content and file paths
3. Review for correctness, regressions, security, maintainability risk, and missing tests
4. Classify findings by severity (Critical, Major, Minor, Suggestion) with concrete file and line references
5. Present findings first, ordered by severity; keep the closing summary brief and only after findings
The line at the top of this page pins the label git:20260413.049789b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_5qbtvkaqmxfvj2tl
GET https://markdownregistry.com/api/v1/resolve?ref=josstei/maestro-orchestrate/review-code
GET https://markdownregistry.com/api/v1/blob/7c72b59de577fcf18fd47958d5dca23304a6fd935346128116ea26606386e4f5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
josstei/maestro-orchestrate · claude/skills/a11y-audit/SKILL.md · Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader…
josstei/maestro-orchestrate · claude/skills/compliance-check/SKILL.md · Run a Maestro-style regulatory compliance review for GDPR/CCPA, cookie consent, data handling, and licensing
josstei/maestro-orchestrate · claude/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
josstei/maestro-orchestrate · claude/skills/perf-check/SKILL.md · Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning
josstei/maestro-orchestrate · claude/skills/review-code/SKILL.md · Perform a Maestro-style code review with findings ordered by severity and concrete file references
aiskillstore/marketplace · skills/0xmsc/review-code/SKILL.md · Provides a structured workflow for planning and executing code reviews like a senior engineer. Use when asked to review…
tobihagemann/turbo · codex/skills/review-code/SKILL.md · Review code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage…
tobihagemann/turbo · claude/skills/review-code/SKILL.md · Review code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage…
blackbelttechnology/pi-agent-dashboard · packages/eng-disciplines/.pi/skills/review-code/SKILL.md · Review a code change well — engine-agnostic critical review discipline for an inline dev loop. Defines what to look for…
doodledood/manifest-dev · claude-plugins/manifest-dev/skills/review-code/SKILL.md · Review a change along one specific quality dimension — bugs, design, simplicity, maintainability, testability, test…
