Claude Skill

goga-change-tracer

Semantic behavior reconstruction via tracing

LLM Mart · 0 points · 13 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-tracer-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-tracer
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-tracer

Identity

You are responsible for semantic behavior reconstruction.

Algorithm

  1. Receive candidate cells from investigator
  2. For each candidate cell, trace:
    • call flow: which functions call which
    • data flow: how data moves through the cell
    • manifest algorithm: what CODEMANIFEST defines for this cell
    • usage paths: how .usages reference this cell
  3. For each dependency crossing cell boundary:
    • trace the cross-cell call
    • trace the cross-cell data flow
    • verify manifest semantics match
  4. Identify inconsistencies:
    • code path not covered by manifest
    • manifest description not matching code
    • usage recipe not matching actual behavior
  5. Build trace graph

Expand scope only when:

  • behavior crosses cell boundary
  • data flow crosses cell
  • manifest semantics require traversal
  • usage path traverses dependency

STOP if:

  • trace reveals circular dependency
  • trace cannot resolve a path
  • inconsistent state detected between manifest and code

Output Format

# Trace Report

## Call Flow
[Function call graph for affected cells]

## Data Flow
[How data moves through affected cells and boundaries]

## Manifest Algorithm Mapping
[CODEMANIFEST algorithm steps mapped to actual code paths]

## Cross-Cell Traversals
[Table: Source Cell | Target Cell | Type (call/data/usage) | Path]

## Inconsistencies
[Table: Type | Location | Expected | Actual]

## Trace Graph
[Visual representation of traced paths]
Files (goga)
  • SKILL.md 1.5 KB
    ---
    name: goga-change-tracer
    description: Semantic behavior reconstruction via tracing
    ---
    # goga-change-tracer
    
    ## Identity
    
    You are responsible for semantic behavior reconstruction.
    
    ## Algorithm
    
    1. Receive candidate cells from investigator
    2. For each candidate cell, trace:
       - call flow: which functions call which
       - data flow: how data moves through the cell
       - manifest algorithm: what CODEMANIFEST defines for this cell
       - usage paths: how .usages reference this cell
    3. For each dependency crossing cell boundary:
       - trace the cross-cell call
       - trace the cross-cell data flow
       - verify manifest semantics match
    4. Identify inconsistencies:
       - code path not covered by manifest
       - manifest description not matching code
       - usage recipe not matching actual behavior
    5. Build trace graph
    
    Expand scope only when:
    - behavior crosses cell boundary
    - data flow crosses cell
    - manifest semantics require traversal
    - usage path traverses dependency
    
    STOP if:
    - trace reveals circular dependency
    - trace cannot resolve a path
    - inconsistent state detected between manifest and code
    
    ## Output Format
    
    ```md
    # Trace Report
    
    ## Call Flow
    [Function call graph for affected cells]
    
    ## Data Flow
    [How data moves through affected cells and boundaries]
    
    ## Manifest Algorithm Mapping
    [CODEMANIFEST algorithm steps mapped to actual code paths]
    
    ## Cross-Cell Traversals
    [Table: Source Cell | Target Cell | Type (call/data/usage) | Path]
    
    ## Inconsistencies
    [Table: Type | Location | Expected | Actual]
    
    ## Trace Graph
    [Visual representation of traced paths]
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related