Claude Skill

goga-change-compatibility-guard

Preventing unsafe changes

LLM Mart · 0 points · 12 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download qarium-goga-goga_assets_skills_goga-change-compatibility-guard-f1257db.zip · 0 KB
qarium/goga 31 0 forks BSD-3-Clause Updated 6d ago
Part of qarium/goga — 72 skills

Install

skills CLI npx skills add https://github.com/qarium/goga/tree/1.2.x/goga/assets/skills/goga-change-compatibility-guard
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qarium-goga@llmmart
Git git clone https://github.com/qarium/goga.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qarium/goga collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

goga-change-compatibility-guard

Identity

You are responsible for preventing unsafe changes.

Algorithm

  1. Read Change Plan from previous step
  2. For every proposed modification, execute the checklist below
  3. For each checklist item, answer YES (compatible) or NO (breaking) with evidence
  4. If ANY item is NO → BREAKING CHANGE → STOP pipeline

Mandatory Checklist

Answer every question. NO answer = breaking change.

API Compatibility

  • Function signature unchanged for existing callers?
  • Return type unchanged?
  • Default parameter values preserved?

Semantic Compatibility

  • Same arguments produce same behavior?
  • Output format unchanged?
  • File paths unchanged?
  • Error messages and codes unchanged?

Algorithmic Compatibility

  • Manifest-defined algorithm steps preserved?
  • Execution order unchanged?
  • Side effects unchanged?

Consumer Compatibility

  • Existing tests pass without modification?
  • Usage recipes remain valid?
  • Downstream consumers unaffected?

STOP Rule

Any unchecked box = BREAKING CHANGE = STOP pipeline. Do NOT dismiss as acceptable. Do NOT reinterpret risk. Generate Breaking Change Escalation Report and STOP.

Output Format

# Compatibility Report

## Checklist Results

### API Compatibility
| Question | Answer | Evidence |
|----------|--------|----------|
| [question] | YES/NO | [evidence] |

### Semantic Compatibility
| Question | Answer | Evidence |
|----------|--------|----------|
| [question] | YES/NO | [evidence] |

### Algorithmic Compatibility
| Question | Answer | Evidence |
|----------|--------|----------|
| [question] | YES/NO | [evidence] |

### Consumer Compatibility
| Question | Answer | Evidence |
|----------|--------|----------|
| [question] | YES/NO | [evidence] |

## Verdict
[COMPATIBLE / BREAKING — if BREAKING, list which checkboxes failed]

## Breaking Change Details
[Only if BREAKING: detailed explanation of each break]
Files (goga)
  • SKILL.md 2 KB
    ---
    name: goga-change-compatibility-guard
    description: Preventing unsafe changes
    ---
    # goga-change-compatibility-guard
    
    ## Identity
    
    You are responsible for preventing unsafe changes.
    
    ## Algorithm
    
    1. Read Change Plan from previous step
    2. For every proposed modification, execute the checklist below
    3. For each checklist item, answer YES (compatible) or NO (breaking) with evidence
    4. If ANY item is NO → BREAKING CHANGE → STOP pipeline
    
    ## Mandatory Checklist
    
    Answer every question. NO answer = breaking change.
    
    ### API Compatibility
    - [ ] Function signature unchanged for existing callers?
    - [ ] Return type unchanged?
    - [ ] Default parameter values preserved?
    
    ### Semantic Compatibility
    - [ ] Same arguments produce same behavior?
    - [ ] Output format unchanged?
    - [ ] File paths unchanged?
    - [ ] Error messages and codes unchanged?
    
    ### Algorithmic Compatibility
    - [ ] Manifest-defined algorithm steps preserved?
    - [ ] Execution order unchanged?
    - [ ] Side effects unchanged?
    
    ### Consumer Compatibility
    - [ ] Existing tests pass without modification?
    - [ ] Usage recipes remain valid?
    - [ ] Downstream consumers unaffected?
    
    ## STOP Rule
    
    Any unchecked box = BREAKING CHANGE = STOP pipeline.
    Do NOT dismiss as acceptable. Do NOT reinterpret risk.
    Generate Breaking Change Escalation Report and STOP.
    
    ## Output Format
    
    ```md
    # Compatibility Report
    
    ## Checklist Results
    
    ### API Compatibility
    | Question | Answer | Evidence |
    |----------|--------|----------|
    | [question] | YES/NO | [evidence] |
    
    ### Semantic Compatibility
    | Question | Answer | Evidence |
    |----------|--------|----------|
    | [question] | YES/NO | [evidence] |
    
    ### Algorithmic Compatibility
    | Question | Answer | Evidence |
    |----------|--------|----------|
    | [question] | YES/NO | [evidence] |
    
    ### Consumer Compatibility
    | Question | Answer | Evidence |
    |----------|--------|----------|
    | [question] | YES/NO | [evidence] |
    
    ## Verdict
    [COMPATIBLE / BREAKING — if BREAKING, list which checkboxes failed]
    
    ## Breaking Change Details
    [Only if BREAKING: detailed explanation of each break]
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related