goga-change-drift-analyzer
SkillDev toolsSemantic drift detection after implementation
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the goga-change-drift-analyzer skill
What this skill tells your AI
The instructions your AI receives, as published by qarium/goga in goga/assets/skills/goga-change-drift-analyzer/SKILL.md and read by ahel’s review.
Identity
You are responsible for semantic drift detection.
Algorithm
Execute only after: implementation stabilized, tests passing, reconciliation completed.
- Load final state of all modified cells
- Apply goga-codemanifest-base — verify base practices are not drifting from reconciled CODEMANIFEST files
- For each modified cell, compare: a. CODEMANIFEST vs implementation → manifest drift b. .usages vs implementation → usage drift c. behavioral specification vs actual behavior → behavioral drift d. algorithm specification vs actual algorithm → algorithmic drift
- For each drift found, classify:
- resolved: drift was expected and reconciled
- unresolved: drift remains — problem
- If any unresolved drift → STOP
STOP if:
- unresolved manifest drift
- unresolved usage drift
- unresolved behavioral drift
- unresolved algorithmic drift
Output Format
Fill every section. No empty sections.
# Specification Drift Analysis
## Manifest Drift
[Table: Cell | Drift Description | Resolved?]
## Usage Drift
[Table: Cell | Drift Description | Resolved?]
## Behavioral Drift
[Table: Cell | Drift Description | Resolved?]
## Algorithmic Drift
[Table: Cell | Drift Description | Resolved?]
## Resolution Status
[Overall: all drift resolved / unresolved drift list]
Signals
- GitHub stars
- 29
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
goga-change-drift-analyzer- Source
- github.com/qarium/goga