configure

Edit comb plugin configuration files with layered JSON merge semantics.

Updated May 4, 2026
One-click install
npx skills add https://github.com/olioskar/comb-the-desert-claude-plugin --skill configure-olioskar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure
Source: https://github.com/olioskar/comb-the-desert-claude-plugin/tree/main/skills/configure
Command: npx skills add https://github.com/olioskar/comb-the-desert-claude-plugin --skill configure-olioskar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely change comb plugin settings without manually editing layered JSON, reducing mistakes when you need to update review paths, models, agents, or directive behavior.

Core Features & Use Cases

  • Config Inspection: Reads the shipped defaults plus global and project overrides to show the effective comb configuration before any change.
  • Targeted Editing: Updates project or global comb.config.json files using the plugin's deep-merge rules, including null-as-delete behavior for disabling agents.
  • Practical Scenarios: Use it to move review reports, change the base branch, swap models for review or fix steps, disable an agent, or point comb at custom directive files.

Quick Start

Ask the skill to update your comb configuration for the scope you want and describe the exact setting changes you need.

Frequently Asked Questions about configure

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

FAQPage Schema
How do I safely update comb plugin configuration files in Claude Code?

Comb plugin configuration files are updated by applying deep merge rules across defaults, global overrides, and project overrides, ensuring safe JSON validation without manual editing errors.

How does deep merge configuration work when changing model assignments or agent palettes?

Deep merge configuration resolves layered JSON by combining defaults with global and project overrides, allowing targeted updates to model assignments and agent palettes while preserving unaffected settings.

Can I disable a specific agent in comb config without deleting the entire configuration?

Yes, disabling a specific agent uses null-as-delete handling within the deep merge semantics, letting you selectively disable agents in project or global comb.config.json files without removing the entire configuration.

What's the best way to change review paths and base branch settings for Claude Code workflows?

Changing review paths and base branch settings is done by targeting the project or global scope in comb.config.json, applying the plugin's deep merge rules to update only the specified configuration values safely.

Does comb configuration support both project-level and global-level scope overrides?

Yes, comb configuration supports both project and global scopes, resolving layered overrides across shipped defaults, global comb.config.json, and project-level files using deep merge semantics to produce the effective configuration.

Why does my comb config JSON validation fail after manually editing layered configuration files?

JSON validation fails when manual edits break the deep merge structure or introduce invalid syntax, which is why targeted editing through proper configuration resolution prevents these layered override conflicts.