campusflow-quality-guardian

Assess risks and inconsistencies in proposed CampusFlow changes before implementation.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Mateo1099/CampusFlow --skill campusflow-quality-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: campusflow-quality-guardian
Source: https://github.com/Mateo1099/CampusFlow/tree/main/.agents/skills/campusflow-quality-guardian
Command: npx skills add https://github.com/Mateo1099/CampusFlow --skill campusflow-quality-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a quality and coherence guardian for CampusFlow, preventing architectural drift and unnoticed regressions by evaluating proposed changes before implementation.

Core Features & Use Cases

  • Evaluate changes across UI, state management, services, database, auth, and persistence to guard consistency.
  • Check architectural coherence, naming conventions, data integrity, and user flows.
  • Provide risk ratings, guardrail recommendations, and phased implementation guidance to protect project integrity.

Quick Start

Provide a proposed CampusFlow change description and let the skill output a risk assessment and guardrails.

Frequently Asked Questions about campusflow-quality-guardian

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

FAQPage Schema
How do I assess architectural risks before implementing changes in a React and Supabase application?

To assess architectural risks, evaluate the proposed change against UI, state, services, database, authentication, and persistence layers. This identifies inconsistencies and potential regressions across the React and Supabase stack before implementation begins.

What is a pre-merge risk assessment for frontend and backend consistency?

A pre-merge risk assessment is a structured evaluation of cross-cutting impacts, data integrity, and naming consistency. It outputs risk ratings and guardrail recommendations to prevent architectural drift and unnoticed regressions.

How do I check if a database schema change will cause state management regressions in React?

You check for regressions by analyzing the proposed database change against the React state and persistence layers. This ensures data integrity, validates user flows, and highlights cross-cutting impacts before the schema migration occurs.

Does this quality review provide rollback plans for Supabase authentication updates?

Yes, the quality review provides safe rollback or migration plans for Supabase authentication updates. It evaluates potential regressions and outputs actionable safeguards to maintain architectural coherence during the update.

What do I need to provide to get a structured risk assessment for my UI changes?

You need to provide a clear description of the proposed UI change. The assessment then checks for cross-cutting impacts, naming consistency, and user flow integrity to output actionable guardrails and phased implementation guidance.