Critical Gate Check

Analyze Git code changes for destructive operations without blocking commits.

2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/rafaelportugal/chama --skill critical-gate-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Critical Gate Check
Source: https://github.com/rafaelportugal/chama/tree/main/skills/gate-check
Command: npx skills add https://github.com/rafaelportugal/chama --skill critical-gate-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a non-blocking way to analyze code changes for destructive operations, allowing users to identify potential issues before they impact the codebase.

Core Features & Use Cases

  • Critical Gate Analysis: Inspects code changes for potentially harmful operations.
  • Non-blocking: Reports findings without preventing commits or merges.
  • Use Case: Before merging a pull request, use this Skill to ensure that no destructive changes have been made.

Quick Start

Run the critical gate check on the current working tree with /chama:gate-check.

Frequently Asked Questions about Critical Gate Check

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

FAQPage Schema
How do I check for destructive code changes before a git commit?

You can check for destructive code changes by running a pre-commit analysis script on your git repository to identify harmful operations before they impact the codebase.

Can I analyze code for harmful operations without blocking a git commit?

Yes, non-blocking code analysis reports potentially destructive operations without preventing commits or merges, allowing you to identify issues while maintaining workflow continuity.

What is a non-blocking critical gate check in code review?

A non-blocking critical gate check inspects code changes during code review to detect harmful operations, reporting findings without halting the pull request merging process.

Do I need bash to run a pre-commit code analysis script?

Yes, you need bash installed in your environment to execute the script required for analyzing the codebase and detecting destructive git repository changes.

How do I scan a git working tree for destructive operations?

You scan a git working tree for destructive operations by running the gate check command, which analyzes current code changes and reports any harmful modifications found.

What is the best way to detect harmful code changes before merging a pull request?

The best way to detect harmful code changes before merging is to perform a non-blocking critical gate analysis, which inspects repository modifications and reports destructive operations without interrupting the process.