Goga Accept Scope
Defines the acceptance scope — the set of cells for a given functionality
Install
$ agentstack add skill-qarium-goga-goga-accept-scope ✓ 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-accept-scope) 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-accept-scope
Identity
You are responsible for defining the acceptance scope — identifying the set of cells associated with a given functionality.
Algorithm
Determine acceptance scope
Acceptance operates at the functionality level. One functionality may span one or more cells.
Resolve the scope:
- Arguments contain a functionality description or path — use as ``
- Arguments are empty — analyze
git diffto identify changed files - No changes found or scope is ambiguous — prompt the user via AskUserQuestion:
- question: "Which functionality should undergo acceptance?"
- header: "Acceptance scope"
- multiSelect: false
- options:
- label: "Branch changes", description: "Determine from git diff"
- label: "Specific functionality", description: "Provide a functionality description"
- label: "All project cells", description: "Full acceptance"
Map scope to cells
- Load the project schema:
goga schema - Match the functionality description or
git diffresults to cells in the schema - For each matched cell:
a. Verify the CODEMANIFEST file exists b. Load the CODEMANIFEST c. Verify the .usages/ directory exists d. Classify change types: CODE / MANIFEST / USAGE / TEST
- Discover dependent cells — cells that import the matched cells
- Classify each dependency:
- DIRECT — imports a changed API
- TRANSITIVE — imports a DIRECT dependency
- Generate the Acceptance Scope Report
STOP if:
- No cells are discovered
- A cell lacks a CODEMANIFEST
- The scope is ambiguous
Output format
Complete every section. Empty sections are not allowed.
# Acceptance Scope Report
## Data source
[How the scope was resolved: arguments, git diff, or user selection]
## Functionality
[Functionality description, if determined]
## Cells for acceptance
[Table: Cell | Path | Change types (CODE/MANIFEST/USAGE/TEST)]
## Affected dependencies
[Table: Dependent cell | Dependency type (DIRECT/TRANSITIVE) | Impact assessment]
## Scope summary
[Total cells, total files, distribution by change categories]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.