validation-guard

Enforce linting, rule compliance, and integrity checks in Phaser projects.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/GiantCroissant-Lunar/proto-breakout --skill validation-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation-guard
Source: https://github.com/GiantCroissant-Lunar/proto-breakout/tree/main/.agent/skills/00-meta/validation-guard
Command: npx skills add https://github.com/GiantCroissant-Lunar/proto-breakout --skill validation-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-implementation verification — checks Phaser project code quality, mandatory rule compliance, and linting. Run after completing implementation work to catch violations before committing.

Core Features & Use Cases

  • Linting
  • Mandatory rules scanning for violations
  • Phaser project integrity checks
  • Pre-commit dry-run

Quick Start

Run this skill after implementing a feature to verify code quality before committing.

Frequently Asked Questions about validation-guard

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

FAQPage Schema
How do I run a pre-commit dry-run to check Phaser code quality?

To check Phaser code quality before committing, run a validation gate that scans modified files for linting errors, mandatory rule violations, and Phaser integrity issues, outputting a validation report with pre-commit readiness status.

What is a post-implementation quality gate for Phaser projects?

A post-implementation quality gate verifies Phaser project code quality by enforcing linting, mandatory rule compliance, and integrity checks after implementing features, producing a validation report to ensure changes meet project standards.

How do I enforce mandatory rules and linting in a Phaser project?

You can enforce mandatory rules and linting in a Phaser project by applying a validation guard that scans modified files for rule violations and linting errors, generating a report detailing lint status, mandatory rule violations, and Phaser integrity status.

Does this validation check work with existing Phaser integrity checks?

Yes, this validation process integrates Phaser integrity checks alongside standard linting and mandatory rule scanning across all modified files, producing a comprehensive validation report that confirms project standards are met before committing.

When should I run a validation report for lint status and rule compliance?

Run the validation report for lint status and rule compliance after implementing features or modifying code and before committing, ensuring new changes meet project standards across all modified files and achieve pre-commit readiness.