ica-get-setting

Fetch configuration values from ICA's multi-layer hierarchy using dot notation.

10|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/intelligentcode-ai/intelligent-code-agents --skill ica-get-setting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ica-get-setting
Source: https://github.com/intelligentcode-ai/intelligent-code-agents/tree/main/src/skills/ica-get-setting
Command: npx skills add https://github.com/intelligentcode-ai/intelligent-code-agents --skill ica-get-setting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ICA configurations are scattered across embedded, project, user, and system defaults, making it hard to reliably fetch the current value for a given setting.

Core Features & Use Cases

  • Dot-notated lookups: Retrieve nested keys like git.privacy or paths.memory from the configuration hierarchy.
  • Fallback handling: Provide a default value when a key is not found to prevent action disruption.
  • Common use cases: Validate autonomy.level before performing tasks; determine team.default_reviewer before assignments.
  • Example: fetch git.privacy to decide whether to strip AI mentions in commits.

Quick Start

Run /ica-get-setting <setting_key> [default_value] to fetch a configuration value from ICA's hierarchy.

Frequently Asked Questions about ica-get-setting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve nested configuration values using dot notation?

You can retrieve nested configuration values by supplying a dot-notated key path, such as git.privacy or paths.memory, to fetch the exact setting from the hierarchy.

How does hierarchical configuration resolution work across multiple layers?

Hierarchical configuration resolution works by checking embedded, project, user, and system config layers sequentially, returning the first matching value found for the requested key.

What happens if a requested configuration key is missing or empty?

If a requested configuration key is missing or empty, the lookup reports an error, unless you provide a fallback default value to prevent action disruption.

Can I provide a fallback default value when fetching settings?

Yes, you can provide a fallback default value when fetching settings by passing it as the second argument, which is returned if the key is not found in any layer.

How do I validate autonomy level before performing tasks?

To validate autonomy level before performing tasks, fetch the autonomy.level configuration value to check the current permission setting and ensure the action is permitted.