Home / josstei / maestro-orchestrate · GitHub

review-code SKILL.md skillA

review-code from josstei/maestro-orchestrate is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add josstei/maestro-orchestrate/review-code@git:20260416.22b788d

Pins git:20260416.22b788d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: josstei/maestro-orchestrate
Path: claude/skills/review-code/SKILL.md
Versions recorded: 1
Latest version: git:20260416.22b788d, committed Apr 16, 2026
Size: 1,057 bytes
Repository stars: 486
License: Apache-2.0

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

# Maestro Review Code

Call `get_skill_content` with resources: ["architecture"].

## Protocol

Before delegating, call `get_skill_content` with resources: ["delegation"] and follow the returned methodology.

## 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

## Constraints

- Do not bury findings behind a long overview
- Every finding must reference a specific file and line number -- no speculative issues
- If no findings exist, say so explicitly and note residual testing gaps

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add josstei/maestro-orchestrate/review-code@sha256:043d178f3a8994dd

The line at the top of this page pins the label git:20260416.22b788d, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_prh7ovw5jckodi3v.svg)](https://markdownregistry.com/a/art_prh7ovw5jckodi3v)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Apr 16, 2026.

version	committed	commit	size	audit
git:20260416.22b788d latest	2026-04-16	22b788d	1,057 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1057 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

josstei/maestro-orchestrate · 486 stars · license Apache-2.0 · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_prh7ovw5jckodi3v
GET https://markdownregistry.com/api/v1/resolve?ref=josstei/maestro-orchestrate/review-code
GET https://markdownregistry.com/api/v1/blob/043d178f3a8994dd739716b3dd4cba1dd46fac1ea48078ed64d803e9a0506a29

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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from josstei/maestro-orchestrate

a11y-audit SKILL.md skill

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…