One-click install
npx skills add https://github.com/samuelcastro/skills --skill super-review-samuelcastro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-review
Source: https://github.com/samuelcastro/skills/tree/main/super-review
Command: npx skills add https://github.com/samuelcastro/skills --skill super-review-samuelcastro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

super-review helps you safely decide whether a branch or PR can be merged by inspecting code, architecture, and release readiness while clearly separating verified evidence from assumptions.

Core Features & Use Cases

  • Severity-classified review findings: organizes issues into blocker / should-fix / nit / human-gate so you know what must be resolved before merging.
  • Actionable routing to the right skill: hands implementation work to the appropriate producer (e.g., feature work to super-build, functional regressions to super-qa, visual/design issues to super-ux) instead of silently editing code.
  • Merge-readiness verdict with verification evidence: outputs a clear final status such as merge-ready, blocked, human-gated, or unverified, including what was verified and how.

Quick Start

Ask your AI to review this branch for merge readiness and route any blockers to the appropriate producer workflow with verification evidence.

Frequently Asked Questions about super-review

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

FAQPage Schema
How do I verify pull request merge readiness with evidence?

Pull request merge readiness is verified by inspecting code changes, architecture, security risks, and release-readiness signals. The process separates verified evidence from assumptions and outputs a final status of merge-ready, blocked, human-gated, or unverified.

What is the best way to classify code review findings before merging a branch?

Code review findings are classified by severity into blocker, should-fix, nit, and human-gate categories. This severity classification helps developers know exactly what issues must be resolved before a branch can be safely merged.

How do I route pull request issues to the right automated workflow?

Routing pull request issues to the right workflow involves handing implementation work to the appropriate producer skill, such as directing feature work to super-build, functional regressions to super-qa, and visual issues to super-ux instead of silently editing code.

Can I inspect a branch for security risks and architecture issues before release?

Yes, branch inspection workflows can review code changes, architecture, and security risks before release. This inspection determines merge readiness by producing severity-classified findings and actionable next steps with verification evidence.

Why does a pull request get marked as human-gated during code review?

A pull request is marked as human-gated when automated review cannot fully verify the changes and requires manual intervention. This status ensures that merge readiness is only confirmed when explicit verification evidence is present or a human approves it.