Menú
Quality review skill for verifying complex changes against criteria. Use for multi-file changes, new features, or before important commits. Skip for trivial fixes and quick iterations.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when working with mise - creating/editing mise.toml or .mise.toml files, defining tasks with usage field arguments, managing dev tools and environments, configuring hooks, or when user mentions mise configuration.
Prisma 7 ORM with PostgreSQL — schema design, migrations, seeding, and Railway deployment patterns. This skill should be used when setting up Prisma in a new project, writing migrations, managing database schemas, or deploying Prisma-backed services to Railway.
Railway deployment and infrastructure management skill. This skill should be used when deploying applications to Railway, managing Railway services, checking deployment status, viewing logs, configuring environment variables, or troubleshooting Railway deployments.
NestJS 11 backend patterns with Fastify, modular architecture, guards, pipes, and Railway deployment. This skill should be used when building NestJS APIs, setting up backend services, or creating REST/GraphQL endpoints with NestJS.
shadcn/studio component library with MCP integration, theme generation, and block patterns. This skill should be used when building UI with shadcn components, selecting dashboard layouts, or generating landing pages. Canonical source for all shadcn-based work.
Theme generation with tweakcn for shadcn/ui and Magic UI animations. Use when setting up project themes, customizing color schemes, adding dark mode, or integrating animated components.
| name | judge |
| description | Quality review skill for verifying complex changes against criteria. Use for multi-file changes, new features, or before important commits. Skip for trivial fixes and quick iterations. |
| skill_type | atomic |
Quality review and evaluation skill that verifies completed work against defined criteria. Part of the two-tier multi-agent architecture where Judge evaluates worker output.
Inputs:
Outputs:
Success Criteria:
Invoke the judge skill:
Skip the judge skill for:
Collect the materials needed for review:
For each acceptance criterion:
Use this evaluation format:
## Review: [Work Description]
### Criteria Evaluation
| Criterion | Status | Evidence |
|-----------|--------|----------|
| [Criterion 1] | PASS/FAIL/PARTIAL | [Evidence] |
| [Criterion 2] | PASS/FAIL/PARTIAL | [Evidence] |
### Issues Found
1. [Issue description]
- **Severity**: Critical/Major/Minor
- **Location**: [File/line]
- **Fix**: [Recommended action]
### Verdict
**PASS** / **FAIL** / **PASS WITH NOTES**
[Summary of decision]
Evaluate across these dimensions based on work type:
| Dimension | Check |
|---|---|
| Correctness | Does it do what was specified? |
| Completeness | Are all criteria addressed? |
| Quality | No obvious bugs, edge cases handled? |
| Style | Follows project conventions? |
| Scope | No scope creep beyond criteria? |
| Dimension | Check |
|---|---|
| Accuracy | Information is correct? |
| Completeness | All required sections present? |
| Format | Follows expected structure? |
| Clarity | Understandable to target audience? |
| Dimension | Check |
|---|---|
| Functionality | Works as expected? |
| Security | No exposed secrets, proper permissions? |
| Idempotency | Can be run again safely? |
| Documentation | Changes documented? |
| Level | Definition | Action |
|---|---|---|
| Critical | Blocks functionality, security issue, data loss risk | Must fix before proceeding |
| Major | Significant deviation from spec, poor UX | Should fix before commit |
| Minor | Style issues, minor improvements | Can note for future |
All criteria met, no critical/major issues. Work can proceed.
Critical issues found OR acceptance criteria not met. Work must be revised.
Provide:
All criteria met, but minor issues noted. Work can proceed with awareness of noted items.
When used in orchestrated workflows:
This creates the planner/worker/judge pattern that scales.
For rapid reviews, use this checklist:
## Quick Review
- [ ] All acceptance criteria addressed
- [ ] No obvious bugs or errors
- [ ] Follows project conventions
- [ ] No scope creep
- [ ] Ready to commit/proceed
**Verdict**: PASS / FAIL
See references/review-criteria.md for detailed review criteria by skill type.