myco:safe-config-updates

Enforce a single YAML write gate for myco.yaml config updates.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill myco-safe-config-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:safe-config-updates
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/safe-config-updates
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-safe-config-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuration drift and data loss happen when multiple code paths write myco.yaml or when UI forms overwrite sections they don't own. This skill enforces a single YAML write gate via updateConfig() and a spread-before-overlay pattern in forms, preventing silent key drops and ensuring full-state mutations are preserved.

Core Features & Use Cases

  • Enforces a single gate for YAML writes to avoid race conditions and data loss.
  • Promotes spread-before-overlay in React settings forms to preserve unrelated keys.
  • Enables patch-based, field-level updates via ScopedField and the scoped config API.
  • Documents and applies the two-tier scoped config model (team/shared myco.yaml and local.yaml overrides).
  • Provides guidance for adding new scoped fields, lifecycle considerations, and in-process reconciliation.

Quick Start

Always route changes through updateConfig and preserve existing keys by spreading the original config before applying overlays.

Frequently Asked Questions about myco:safe-config-updates

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

FAQPage Schema
How do I prevent configuration drift and data loss when writing to YAML config files?

Preventing YAML configuration drift requires enforcing a single write gate through an updateConfig function, ensuring all mutations follow deterministic patching rules rather than allowing multiple code paths to write directly.

Why does my React settings form overwrite unrelated keys in my YAML config?

React settings forms overwrite unrelated YAML keys when they replace the entire config object instead of using a spread-before-overlay pattern, which preserves existing keys by copying the original state before applying targeted field updates.

What is the two-tier scoped config model for managing team and local settings?

The two-tier scoped config model separates shared team settings in myco.yaml from personal overrides in local.yaml, allowing deterministic patching to apply field-level updates without losing team-level configuration defaults.

How do I apply idempotent patches to update config fields safely?

Idempotent config patches are applied by routing changes through updateConfig guards with ScopedField rules, ensuring predictable field-level updates that produce identical results across multiple executions without silent key drops.

Can I use CLI config mutations alongside React form updates without causing race conditions?

CLI config mutations and React form updates can coexist safely when both route through the single YAML write gate, preventing race conditions by serializing all write operations through updateConfig and deterministic patch enforcement.