icc-get-setting

Retrieve resolved configuration values from the ICC hierarchy with dot-notation lookup.

35|3|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill icc-get-setting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: icc-get-setting
Source: https://github.com/intelligentcode-ai/intelligent-claude-code/tree/main/src/skills/icc-get-setting
Command: npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill icc-get-setting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reliable way to read configuration values from the ICC configuration hierarchy, enabling dynamic behavior based on environment, user role, and project settings.

Core Features & Use Cases

  • Dot notation access: Retrieve nested settings like git.privacy or paths.memory using a single key.
  • Defaults and fallbacks: Return a default_value when a setting is missing.
  • Precedence rules: Resolve values following embedded, project, user, and system sources.

Quick Start

ICC Get Setting: /icc-get-setting git.privacy

Frequently Asked Questions about icc-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-notation key like git.privacy or paths.memory to fetch the resolved setting from the configuration hierarchy.

What is the precedence order for resolving project configuration settings?▼

Configuration settings are resolved by checking embedded, project, user, and system sources in sequence, applying precedence rules to return the highest-priority available value.

Can I specify a fallback value when a configuration setting is missing?▼

Yes, you can provide a default_value parameter to return a fallback when a specific setting is missing from the embedded, project, user, and system configuration sources.

How do I validate settings like git.privacy and autonomy.level across different environments?▼

You validate settings across environments by querying specific dot-notation keys, which traverse the embedded, project, user, and system configurations to return the resolved setting value.

What configuration keys are supported for retrieving ICC project settings?▼

Supported configuration keys include git.privacy, autonomy.level, paths.*, and team.default_reviewer, which are resolved using precedence rules and default fallbacks.