settings-management

Name: settings-management
Availability: InStock
Author: CodeAlive

Guide updates to coding agent settings files with validation.

119|10|Updated Jan 16, 2026

Search Tags:#hooks #permissions #configuration #model selection #sandbox #profiles #agent settings

Ready to run

npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill settings-management-codealive-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: settings-management
Source: https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/settings-management
Command: npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill settings-management-codealive-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the friction of manually tracking where coding-agent configuration lives and how to correctly update the right settings file across different agent platforms.

Core Features & Use Cases

Unified settings guidance across agents: Covers Claude Code (JSON), Codex CLI (TOML), and OpenCode (JSON/JSONC) including permissions, sandboxing, model selection, profiles, feature flags, providers, hooks, subagents, and skills.
Safe update workflow: Guides you to identify scope (user vs project vs local), read existing configuration first, merge changes, validate JSON, and confirm the final result.
Practical operational reminders: Explicitly reminds you to restart the agent after changes because most settings load at startup.

Quick Start

Ask your AI agent to update your project-scoped Claude Code settings in .claude/settings.json to set the default model to claude-opus-4-7 and enable extended thinking.

Frequently Asked Questions about settings-management

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

FAQPage Schema

How do I update Claude Code agent settings to change the default model?▼

Update Claude Code agent settings by reading the existing .claude/settings.json, merging the new default model value, validating the JSON schema, and restarting the agent so the configuration loads reliably at startup.

What is the correct settings file format for Codex CLI configuration?▼

The correct settings file format for Codex CLI configuration is TOML, whereas Claude Code uses JSON and OpenCode supports JSON or JSONC, requiring format validation before merging permissions, sandbox behavior, or model routing updates.

How do I configure permissions and sandbox behavior across different coding agents?▼

Configure permissions and sandbox behavior by identifying the correct configuration scope (user, project, or local), reading the existing settings file, safely merging the permission and sandbox updates, validating the format, and restarting the coding agent.

Does this settings management workflow support profiles and feature flags for OpenCode?▼

Yes, the settings management workflow supports OpenCode profiles and feature flags by guiding updates to JSON or JSONC configuration files, applying safe merging practices, validating the schema, and reminding you to restart the agent after edits.

Why are my agent configuration changes not taking effect after editing the settings file?▼

Agent configuration changes often fail to take effect because most settings load at startup; you must restart the coding agent after editing and validating the settings file so the updated permissions, hooks, or model routing reliably apply.

What's the best way to safely merge hooks and subagents into an existing agent configuration?▼

The best way to safely merge hooks and subagents is to identify the correct scope, read the existing configuration file first, merge the new entries without overwriting current settings, validate the JSON or TOML schema, and restart the agent.