reviewer

Verify Mastra migration pull requests with runtime checks and structured review criteria.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/brewpirate/acme-frontier-ai --skill reviewer-brewpirate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/skills/reviewer
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill reviewer-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false-positive approvals on Mastra migration pull requests by requiring structured review, independent runtime verification, and evidence-backed conclusions instead of trust in claims alone.

Core Features & Use Cases

  • Independent runtime verification: Reproduces PR claims and compares observed behavior against the submission.
  • Mastra pattern enforcement: Checks diffs for established framework conventions, guardrails, and ownership boundaries.
  • Protocol and streaming review: Audits run-stream, SSE, and event-contract changes for correctness and forward compatibility.
  • Test and PR body inspection: Evaluates coverage quality, artifact-backed proof, deferred work, and dependency clarity.
  • Use case: Review a PR that changes agents, traces, or streaming code and decide whether it is truly ready to merge.

Quick Start

Review this Mastra migration PR, verify the runtime claims independently, and tell me whether it is ready to ship.

Frequently Asked Questions about reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Mastra pull requests with runtime evidence?

You verify Mastra pull requests by reproducing PR claims independently and comparing observed runtime behavior against the submission. This requires structured review, guardrail enforcement, and protocol coverage checks before deciding to merge.

How do I review code changes that touch Mastra streaming and traces?

Reviewing Mastra streaming and traces involves auditing run-stream, SSE, and event-contract changes for correctness and forward compatibility. You must enforce framework conventions, ownership boundaries, and guardrails across the diff.

What is runtime verification for pull request reviews?

Runtime verification for pull request reviews is the process of reproducing claimed behaviors independently to prevent false-positive approvals. It ensures merge decisions are backed by observed evidence rather than trust in submission claims alone.

Does this code review process apply to all files importing from @mastra/*?

Yes, the code review process applies to any pull request touching files importing from @mastra/*, including agents, streaming, and run-stream code. It also handles follow-up re-reviews and cross-PR pattern analysis.

What are the limitations of trusting PR claims without independent execution checks?

Trusting PR claims without independent execution checks risks false-positive approvals on Mastra migrations. It allows unverified streaming, trace, or agent changes to merge, potentially breaking guardrails, protocols, and test coverage.