goga-accept-scope
SkillDev toolsDefines the acceptance scope — the set of cells for a given functionality
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-accept-scope skill
What this skill tells your AI
The instructions your AI receives, as published by qarium/goga in goga/assets/skills/goga-accept-scope/SKILL.md and read by ahel’s review.
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
<target> - 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]
Signals
- GitHub stars
- 29
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
goga-accept-scope- Source
- github.com/qarium/goga