critic-regression

Analyze multiple code repositories to detect regressions and contract conflicts.

3|Updated May 20, 2026

Search Tags:#code review #repository analysis #regression detection #API contract verification #cross-repo scanning

Ready to run

npx skills add https://github.com/iampawan/Manifest --skill critic-regression

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: critic-regression
Source: https://github.com/iampawan/Manifest/tree/main/skills/critic-regression
Command: npx skills add https://github.com/iampawan/Manifest --skill critic-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit identifies potential regressions, conflicts, or coordination requirements across multiple repositories, ensuring that new contracts do not break existing behaviors.

Core Features & Use Cases

Cross-Repo Scanning: Analyze code in multiple repositories (Flutter, Web, Backend, etc.) to detect issues related to a new contract.
Regression Detection: Flags potential regressions and conflicts that might break, conflict with, or require coordination with shipped code.
API Contract Verification: Ensures the contract's API does not conflict with backend implementations and finds related frontend consumers.

Quick Start

Run the 'critic-regression' skill on a new contract to scan for potential issues across all repositories.

Frequently Asked Questions about critic-regression

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

FAQPage Schema

How do I detect regressions across multiple code repositories?▼

Detect regressions across multiple repositories by scanning code against new contracts to identify conflicts, broken behaviors, and coordination requirements. This ensures new API definitions do not disrupt existing frontend or backend implementations.

How do I verify an API contract against backend implementations and frontend consumers?▼

Verify API contracts by analyzing contract content and repository configurations to ensure consistency. This scans for potential conflicts between the contract and shipped code, finding related frontend consumers and backend implementations.

Can I scan local repository clones or do I need GitHub MCP for cross-repo analysis?▼

Cross-repo scanning supports both GitHub MCP and local clones for code retrieval. You can analyze multiple repositories like Flutter, Web, and Backend to detect issues related to a new contract regardless of your retrieval method.

What is cross-repo scanning for code integrity and when do I need it?▼

Cross-repo scanning for code integrity analyzes multiple repositories to detect regressions and conflicts. You need this when introducing new contracts to ensure new definitions do not break existing behaviors across your different codebases.

How do I identify coordination requirements before shipping a new API contract?▼

Identify coordination requirements by running a regression analysis on the new contract across all repositories. This flags potential conflicts and breaks in shipped code, ensuring consistency between the contract and existing implementations.