quality

Review completed cook work and emit a structured stage_message with findings.

218|11|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/poteto/noodle --skill quality-poteto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/poteto/noodle/tree/main/.agents/skills/quality
Command: npx skills add https://github.com/poteto/noodle --skill quality-poteto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Post-cook quality gate. Reviews completed cook work for correctness, scope discipline, and principle compliance. Emits stage_message events with findings.

Core Features & Use Cases

  • Autonomously evaluates the plan phase, commits, and changes against the defined scope.
  • Verifies code quality through standard checks, tests, and runtime verification, and flags high-severity issues.
  • Produces a structured stage_message payload that guides retries, escalations, or approvals.

Quick Start

Trigger this quality gate after cook completion to generate a stage_message with findings.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I automate code review and quality checks on a git diff before committing?

Runtime verification validates code behavior during execution, complementing static analysis by catching high-severity issues through tests and runtime checks to gate pipeline progression with a structured verdict.

What is the best way to enforce scope discipline and prevent scope creep in code commits?

A stage_message report provides a structured payload detailing quality findings, high-severity issues, and a blocking flag, enabling automated pipelines to trigger retries, escalations, or approvals based on the verdict.

How do I run go-vet and standard code quality checks as a post-build pipeline gate?

A stage_message report provides a structured payload detailing quality findings, high-severity issues, and a blocking flag, enabling automated pipelines to trigger retries, escalations, or approvals based on the verdict.

Does runtime verification catch errors that standard code quality checks miss?

Autonomous quality gating evaluates the plan phase, git diff, and commit history against defined scope, verifying code quality and runtime behavior to emit a structured stage_message report without manual intervention.

What does a stage_message report contain for gating CI/CD pipelines?

Evaluating the plan phase and commit history against the defined scope verifies code changes align with original goals, flagging deviations and scope creep to block pipeline progression with a structured verdict.

Can I autonomously gate pipeline progression based on code review findings?

A stage_message report provides a structured payload detailing quality findings, high-severity issues, and a blocking flag, enabling automated pipelines to trigger retries, escalations, or approvals based on the verdict.