# Goga Change Tracer

> Semantic behavior reconstruction via tracing

- Skill: `qarium/goga-change-tracer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add qarium/goga-change-tracer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qarium/goga-change-tracer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: qarium (https://skillmd.com/u/qarium)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qarium/goga-change-tracer

---

# 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]
```