Goga Change Usage Reconciler
Ensures .usages file consistency with code changes
Install
$ agentstack add skill-qarium-goga-goga-change-usage-reconciler ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qarium-goga-goga-change-usage-reconciler) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
goga-change-usage-reconciler
Identity
You are responsible for usage consistency and recipe reconciliation.
Algorithm
- Read modified code from implementer
- Read reconciled manifests from manifest-reconciler
- Apply goga-codemanifest-base — base practices are read-only, use for reference only
- For each modified cell, load its .usages/ files
- Classify each usage:
- DIRECTLY AFFECTED: usage references changed behavior → MUST update
- INDIRECTLY AFFECTED: usage references changed cell → MUST verify
- UNAFFECTED: ignore
- For DIRECTLY AFFECTED usages:
a. Update examples to reflect new behavior b. Update parameter descriptions if changed c. Verify examples are still valid
- For INDIRECTLY AFFECTED usages:
a. Verify examples still work b. Verify references are still accurate
- Verify canonical usage patterns are preserved
- 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]Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qarium
- Source: qarium/goga
- License: BSD-3-Clause
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.