check

Run read-only architecture and code-quality checks before merging.

2|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill check-tmi-apps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor/tree/main/.cursor/skills/check
Command: npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill check-tmi-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an architecture and code-quality gate to ensure structural soundness before changes enter the main branch, delivering confidence without automatic changes.

Core Features & Use Cases

  • Architecture and structure integrity checks to detect drift after refactors.
  • Read-only reporting that surfaces issues and suggests remediation steps.
  • Pre-merge and pre-finish validation to streamline reviews and maintain quality standards.

Quick Start

Run the check pass before merging to surface architecture and style issues.

Frequently Asked Questions about check

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

FAQPage Schema
How do I check architecture quality before merging a branch?

To check architecture quality before merging, run a validation pass that inspects your code changes to surface structural drift and code-quality issues. This pre-merge gate generates a read-only report listing architectural problems and suggesting remediation steps.

What is the best way to detect architecture drift after a code refactor?

Detecting architecture drift after a refactor requires running structure integrity checks on the change-set. This validation process surfaces architectural issues caused by the refactoring and references workflow rules to guide your remediation.

How do I perform a pre-merge code review to ensure structural soundness?

Performing a pre-merge code review involves executing an architecture and code-quality gate on the pending changes. This read-only inspection identifies structural flaws and enforces quality standards without applying automatic modifications to your codebase.

Does the architecture validation gate automatically fix code-quality issues?

Architecture validation does not automatically fix code-quality issues. It operates as a read-only gate that surfaces structural problems and lists architecture checks, providing references to workflow rules so you can manually guide remediation.

When do I need to run pre-merge architecture checks?

Run pre-merge architecture checks during pre-merge gates, post-refactor reviews, and change-set inspections. You need this validation to surface architectural issues and ensure structural soundness before changes enter the main branch.

Can I use this validation as a gate for post-refactor reviews?

You can use this validation as a gate for post-refactor reviews to detect structural drift. It inspects the change-set, enforces a read-only report of architecture and code-quality issues, and references workflow rules to streamline your review process.