self-critique

Name: self-critique
Availability: InStock
Author: GiantCroissant-Lunar

Evaluate implementations against specs and project doctrine using rubric-driven checks.

Updated Aug 27, 2026

Search Tags:#architecture #code-quality #rubric #code-review #specs #evaluate #doctrine

Ready to run

npx skills add https://github.com/GiantCroissant-Lunar/fantasim-world --skill self-critique

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-critique
Source: https://github.com/GiantCroissant-Lunar/fantasim-world/tree/main/.agent/skills/self-critique
Command: npx skills add https://github.com/GiantCroissant-Lunar/fantasim-world --skill self-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an automated self-evaluation loop that reviews a feature's implementation against the project specifications, doctrine, and quality criteria before completion.

Core Features & Use Cases

Iterative evaluation: Repeats scoring against a rubric to surface blockers and drive improvements.
Architecture and contract checks: Ensures alignment with project architecture, interfaces, and data contracts.
Use Case: Before closing a task, run the self-critique to validate spec conformance and readiness for code review.

Quick Start

Run @self-critique after implementing a feature to compare against specs, plan, and rubric, and iterate until PASS

Frequently Asked Questions about self-critique

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

FAQPage Schema

How do I validate code quality against project specs before a code review?▼

To validate code quality before a code review, run an automated self-evaluation loop to score implementations against project specs, doctrine, and rubric criteria. It surfaces blockers and checks architecture compliance to ensure feature readiness.

What is rubric-driven self-evaluation for feature development?▼

Rubric-driven self-evaluation is an automated process that reviews a feature implementation against project specifications and quality criteria. It enforces checks for spec alignment, architecture compliance, and contract stability across iterations.

How do I check architecture compliance and contract stability before closing a task?▼

Check architecture compliance and contract stability by running an iterative evaluation loop against the project doctrine. This ensures alignment with interfaces and data contracts, validating that the implementation meets runnable state criteria.

Can I use automated spec alignment to find blockers during iterations?▼

Yes, you can use automated spec alignment to find blockers during iterations. The evaluation repeats scoring against a rubric to drive improvements and enforce conventions until the implementation passes readiness checks.

Does the self-critique evaluation require external dependencies to run?▼

No, the self-critique evaluation requires no external dependencies to run. It operates independently to compare implementations against the plan, specs, and rubric to validate conformance and readiness for review.

When should I run an automated code review loop in the development workflow?▼

Run an automated code review loop after implementing a feature and before task completion. It applies during feature development and prior to formal code review to validate spec conformance and enforce quality criteria.