compas

Validate code quality and enforce standards across repositories with configurable checks.

Updated Aug 23, 2026

Search Tags:#code quality #ci/cd #validation #developer experience #gatekeeping #compas

Ready to run

npx skills add https://github.com/AmirTlinov/magray-marketplace --skill compas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compas
Source: https://github.com/AmirTlinov/magray-marketplace/tree/main/compas/skills/compas
Command: npx skills add https://github.com/AmirTlinov/magray-marketplace --skill compas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces code quality, consistency, and best practices across repositories, preventing regressions and ensuring maintainability.

Core Features & Use Cases

Quality Validation: Runs checks for code formatting, linting, and other quality metrics.
Gate Enforcement: Implements quality gates (CI-fast, CI, Flagship) to ensure code meets standards before merging.
Tool Management: Manages and integrates project-specific tools and their configurations.
Ratchet Mode: Prevents quality regressions by comparing against established baselines.
Use Case: When submitting a pull request, this Skill automatically validates that all code adheres to project standards, runs essential tests, and ensures no quality has degraded since the last merge.

Quick Start

Run compas validate ratchet to check for quality regressions.

Frequently Asked Questions about compas

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

FAQPage Schema

How do I enforce code quality and consistency in a CI/CD pipeline?▼

You can enforce code quality in a CI/CD pipeline by configuring quality gates that run checks for formatting and linting before code merges. This Skill manages tool manifests and validates code health against established project standards.

What is ratchet mode for preventing code quality regressions?▼

Ratchet mode prevents code quality regressions by comparing new code changes against established baselines. Run the validate ratchet command to ensure no quality has degraded since the last merge, maintaining long-term code health.

Can I use custom quality gates for different pull request validation stages?▼

Yes, you can implement custom quality gates for different stages such as CI-fast, CI, and Flagship. This ensures code meets specific standards at various phases before merging, preventing regressions and ensuring maintainability across repositories.

How do I manage project-specific linting and formatting tool configurations?▼

You manage project-specific linting and formatting tools by integrating repo-side configurations for plugins and tool manifests. This Skill centralizes tool management to ensure consistent code quality validation across your development workflows.

Does this code quality validation tool require external dependencies to run?▼

No, this code quality validation tool operates without external dependencies. It integrates directly with your repo-side configurations to manage quality gates, tool manifests, and baseline comparisons for your CI/CD pipelines.

Why do I need baseline comparisons for code health in my repositories?▼

Baseline comparisons are needed to prevent quality regressions by tracking code health against established standards. Ratchet mode compares current code against these baselines to ensure no quality has degraded since the last merge.