quality-check

Audit repository diffs against canonical doctrine and architectural boundaries.

Updated Aug 27, 2026

Search Tags:#quality-check #lint #code-review #boundaries #typecheck #doctrine #non-regression

Ready to run

npx skills add https://github.com/Deadpool042/Creatyss --skill quality-check-deadpool042

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-check
Source: https://github.com/Deadpool042/Creatyss/tree/main/.codex/skills/quality-check
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill quality-check-deadpool042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the repository against the canonical doctrine and architectural boundaries to prevent drift, ensure consistent structure, and guard against scope creep.

Core Features & Use Cases

Conformance verification against AGENTS.md and the documented architecture, domains, and testing structure
Checks typecheck and lint results to enforce code quality and avoid accidental regressions
Validates changes against the requested scope and boundaries for targeted diffs or zones

Quick Start

Run this skill on the target diff or area to validate conformance with the canonical doctrine and boundaries.

Frequently Asked Questions about quality-check

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

FAQPage Schema

How do I prevent codebase drift from the canonical architecture doctrine?▼

You can verify codebase conformance by auditing target diffs or repository zones against the documented architecture, domains, and testing structure to ensure strict boundary enforcement and prevent architectural drift.

How do I enforce typechecking and linting on targeted code diffs?▼

Enforce typechecking and linting on targeted diffs by applying validation rules to specific repository zones. This checks results to maintain code quality, enforce boundaries, and avoid accidental regressions during changes.

Can I validate changes against requested scope and boundaries for a specific zone?▼

Yes, you can validate changes against requested scope and boundaries by applying the audit to specific repository zones or batches. This targeted approach ensures domain alignment and prevents scope creep in isolated areas.

What is the best way to verify conformance with AGENTS.md architecture rules?▼

The best way to verify conformance with AGENTS.md is to audit the repository against the canonical doctrine. This confirms alignment with documented architecture, domains, and testing structure while enforcing strict validation rules.

Do I need a documented architecture to audit repository zones for non-regression?▼

Yes, you need a canonical doctrine and documented architecture as a baseline. The audit compares your codebase against these established boundaries and validation rules to identify deviations and ensure non-regression.