Claude Skill

goga-codemanifest-base

Load project configuration from .goga/config.yml

LLM Mart · 0 points · 3 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download qarium-goga-goga_assets_skills_goga-codemanifest-base-f1257db.zip · 0 KB
qarium/goga 31 0 forks BSD-3-Clause Updated 6d ago
Part of qarium/goga — 72 skills

Install

skills CLI npx skills add https://github.com/qarium/goga/tree/1.2.x/goga/assets/skills/goga-codemanifest-base
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qarium-goga@llmmart
Git git clone https://github.com/qarium/goga.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qarium/goga collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Load project configuration

Purpose

Loads the project's base usages and annotations from the .goga/config.yml configuration file via goga config CLI commands. These settings define project practices and instructions available to all CODEMANIFEST files.


Behavior

Do not restate the content — apply the loaded usages and annotations in the context of the invoking skill.


Instruction

Step 1: Retrieve the project's base usages

Run goga config codemanifest.usages to retrieve the project's base usages from the codemanifest.usages section in .goga/config.yml. These are project practices available to all CODEMANIFEST files.

Step 2: Retrieve the project's base annotations

Run goga config codemanifest.annotations to retrieve the project's base annotations — text instructions for the AI agent — from the codemanifest.annotations section in .goga/config.yml.

Step 3: Process the result

If the commands return an "Option not found" error, the codemanifest section is absent from .goga/config.yml; no base annotations or usages are defined — record this as a fact.

If the codemanifest section exists:

  1. Read the usage files — for each usage listed in codemanifest.usages, read the corresponding md file from the .goga/usages/ directory. These practices are mandatory when designing all CODEMANIFEST files.

  2. Analyze the base annotations — if annotations contain instructions affecting CODEMANIFEST formation (e.g., structure requirements, conventions, constraints), record them as mandatory design constraints.


Files (goga)
  • SKILL.md 1.7 KB
    ---
    name: goga-codemanifest-base
    description: Load project configuration from .goga/config.yml
    ---
    # Load project configuration
    
    ## Purpose
    
    Loads the project's base usages and annotations from the `.goga/config.yml` configuration file via `goga config` CLI commands.
    These settings define project practices and instructions available to all CODEMANIFEST files.
    
    ---
    
    ## Behavior
    
    Do not restate the content — apply the loaded usages and annotations in the context of the invoking skill.
    
    ---
    
    ## Instruction
    
    ### Step 1: Retrieve the project's base usages
    
    Run `goga config codemanifest.usages` to retrieve the project's base usages from the `codemanifest.usages` section in `.goga/config.yml`.
    These are project practices available to all CODEMANIFEST files.
    
    ### Step 2: Retrieve the project's base annotations
    
    Run `goga config codemanifest.annotations` to retrieve the project's base annotations — text instructions
    for the AI agent — from the `codemanifest.annotations` section in `.goga/config.yml`.
    
    ### Step 3: Process the result
    
    If the commands return an "Option not found" error, the `codemanifest` section is absent from `.goga/config.yml`; no base
    annotations or usages are defined — record this as a fact.
    
    If the `codemanifest` section exists:
    
    1. **Read the usage files** — for each usage listed in `codemanifest.usages`, read the corresponding md file
       from the `.goga/usages/` directory. These practices are mandatory when designing all CODEMANIFEST files.
    
    2. **Analyze the base annotations** — if annotations contain instructions affecting CODEMANIFEST
       formation (e.g., structure requirements, conventions, constraints), record them as mandatory
       design constraints.
    
    ---
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related