/gaia-config-severity

user-facing
Category:
Configuration
Lifecycle phase:
4 -- Implementation
Arguments:
<set|show|clear> [<internal> <verdict>]

What it does

/gaia-config-severity edits the severity section of .gaia/config/project-config.yaml -- the 5-into-3 severity map that translates internal severity bands to gate verdicts. The downstream review system reads this map when composing gate verdicts.

The five internal severity names (Critical, High, Medium, Low, Info) each map to one of three verdicts (BLOCKED, REQUEST_CHANGES, APPROVE). The editor preserves all YAML comments and formatting outside the edited section.

When to use it

  • You want to change which severity levels block a review gate versus which are advisory.
  • You are setting up a new project and need to configure the global severity-to-verdict map.
  • You want to view or reset the current severity configuration.

Prerequisites

  • project-config.yaml must exist. Run /gaia-init to create one if missing.

How to invoke

/gaia-config-severity show
/gaia-config-severity set Critical BLOCKED
/gaia-config-severity set Low APPROVE
/gaia-config-severity clear

What it does step by step

  1. Locate project-config.yaml Resolves the configuration file path via the canonical resolver.
  2. Dispatch subcommand Routes to the deterministic helper script:
    • set <internal> <verdict> -- set or replace a single mapping. Creates the section if absent.
    • show -- print the current map (one line per entry), or "no severity section" when absent.
    • clear -- remove the severity section entirely.
  3. Suggest validation Recommends running /gaia-config-validate to confirm the file still passes schema validation.

Inputs

InputSourceDescription
Project configuration.gaia/config/project-config.yamlThe file containing the severity section.

Outputs

OutputLocationDescription
Updated severity section.gaia/config/project-config.yamlThe modified severity block (comment-preserving).

Example session

> /gaia-config-severity show

severity:
  Critical: BLOCKED
  High: BLOCKED
  Medium: REQUEST_CHANGES
  Low: APPROVE
  Info: APPROVE

> /gaia-config-severity set Medium BLOCKED

severity section updated. Run /gaia-config-validate to verify.

> /gaia-config-severity show

severity:
  Critical: BLOCKED
  High: BLOCKED
  Medium: BLOCKED
  Low: APPROVE
  Info: APPROVE

What to run next

Troubleshooting

no severity section

The section does not exist in your config file. The set subcommand creates it automatically on first write.

Invalid internal severity name

Only the closed set Critical, High, Medium, Low, Info is accepted. Any other value is rejected with exit 1.

Invalid verdict value

Only BLOCKED, REQUEST_CHANGES, APPROVE are accepted. Any other value is rejected with exit 1.