goga-review-cell

Cell Review

Purpose

Reviews a cell across three dimensions and proposes concrete remediation actions for each detected issue. Each action requires explicit user confirmation before execution.

You identify issues, propose solutions, and execute user-approved actions (invoking other skills, editing files).

---

Key Principle

Identify the exact problem before proposing a solution. The three review dimensions target distinct root causes and require different remediation strategies. Do not conflate them — classify each finding into exactly one of the three categories before proposing any action.

User Interaction Rule

Always provide answer options. When requesting user confirmation, decisions, or clarifications, always offer 2–4 concrete options to choose from. Never pose open-ended questions without selectable choices.

---

Steps

Step 1: Load Context

1. Invoke goga-lang-disp via the Skill tool to load the target language skill. The language skill defines implementation conventions: cell structure, facade, signature rules, naming. Examples in other skills may follow naming conventions of one language (e.g., snake_case), while the target language requires different conventions (e.g., PascalCase). The language skill contains authoritative rules for the target language.
2. Load the DSL specification and DSL application principles:
   • Invoke goga-cell via the Skill tool to understand CODEMANIFEST DSL syntax, structural rules, and semantics (cell structure, Imports, Usages, Annotations directives, types, signatures, mutations, embeddings, constraints)
   • Invoke goga-cookbook via the Skill tool to understand cell and CODEMANIFEST working principles (when to use Entity vs Routine, when to apply mutations and embeddings, usage file authoring principles, cell granularity)
   • Critical for accurate analysis: without understanding DSL rules, CODEMANIFEST entries will be misinterpreted
   • Consult the loaded specification and principles whenever CODEMANIFEST entry correctness is uncertain
3. Read the cell's CODEMANIFEST file
4. Parse all entities, methods, properties, imports, usages, annotations, re-exports, and locations
5. Enumerate all source files in the cell directory (excluding .usages/, build artifacts, tests, and other non-contract files)
6. Read all source files corresponding to declared location values
7. Read all .usages/*.md files if the .usages/ directory exists
8. Verify the facade file exists