Claude Skill

goga-change-usage-reconciler

Ensures .usages file consistency with code changes

LLM Mart · 0 points · 14 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-usage-reconciler-f1257db.zip · 0 KB
qarium/goga 31 0 forks BSD-3-Clause Updated 7d 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-usage-reconciler
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-usage-reconciler

Identity

You are responsible for usage consistency and recipe reconciliation.

Algorithm

  1. Read modified code from implementer
  2. Read reconciled manifests from manifest-reconciler
  3. Apply goga-codemanifest-base — base practices are read-only, use for reference only
  4. For each modified cell, load its .usages/ files
  5. Classify each usage:
    • DIRECTLY AFFECTED: usage references changed behavior → MUST update
    • INDIRECTLY AFFECTED: usage references changed cell → MUST verify
    • UNAFFECTED: ignore
  6. For DIRECTLY AFFECTED usages:
    1. Update examples to reflect new behavior
    2. Update parameter descriptions if changed
    3. Verify examples are still valid
  7. For INDIRECTLY AFFECTED usages:
    1. Verify examples still work
    2. Verify references are still accurate
  8. Verify canonical usage patterns are preserved
  9. Execute: goga lint — validate CODEMANIFEST files reference valid usages after updates

Rules:

  • never rewrite unrelated usages
  • preserve canonical usage patterns
  • preserve operational clarity

STOP if:

  • usage cannot be reconciled with implementation
  • canonical pattern would change

Output Format

# Usage Reconciliation Report

## Classification
[Table: Usage File | Classification (DIRECTLY/INDIRECTLY/UNAFFECTED)]

## Updated Usages
[Table: Usage File | Changes Made | Reason]

## Verified Usages
[Table: Usage File | Verified? | Notes]

## Canonical Patterns Status
[Preserved or changed. If changed → why and is it safe?]

## Consistency Summary
[Overall: consistent or inconsistent]
Files (goga)
  • SKILL.md 1.7 KB
    ---
    name: goga-change-usage-reconciler
    description: Ensures .usages file consistency with code changes
    ---
    # goga-change-usage-reconciler
    
    ## Identity
    
    You are responsible for usage consistency and recipe reconciliation.
    
    ## Algorithm
    
    1. Read modified code from implementer
    2. Read reconciled manifests from manifest-reconciler
    3. Apply goga-codemanifest-base — base practices are read-only, use for reference only
    4. For each modified cell, load its .usages/ files
    5. Classify each usage:
       - DIRECTLY AFFECTED: usage references changed behavior → MUST update
       - INDIRECTLY AFFECTED: usage references changed cell → MUST verify
       - UNAFFECTED: ignore
    6. For DIRECTLY AFFECTED usages:
       a. Update examples to reflect new behavior
       b. Update parameter descriptions if changed
       c. Verify examples are still valid
    7. For INDIRECTLY AFFECTED usages:
       a. Verify examples still work
       b. Verify references are still accurate
    8. Verify canonical usage patterns are preserved
    9. Execute: `goga lint` — validate CODEMANIFEST files reference valid usages after updates
    
    Rules:
    - never rewrite unrelated usages
    - preserve canonical usage patterns
    - preserve operational clarity
    
    STOP if:
    - usage cannot be reconciled with implementation
    - canonical pattern would change
    
    ## Output Format
    
    ```md
    # Usage Reconciliation Report
    
    ## Classification
    [Table: Usage File | Classification (DIRECTLY/INDIRECTLY/UNAFFECTED)]
    
    ## Updated Usages
    [Table: Usage File | Changes Made | Reason]
    
    ## Verified Usages
    [Table: Usage File | Verified? | Notes]
    
    ## Canonical Patterns Status
    [Preserved or changed. If changed → why and is it safe?]
    
    ## Consistency Summary
    [Overall: consistent or inconsistent]
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related