agentsclimarketplace

Override management

Skill event4u-app/agent-config/src/skills/override-management

Creates and manages project-level overrides for shared skills, rules, and commands — extending or replacing originals from .augment/ with project-specific behavior in agents/overrides/.From its SKILL.md

Install
npx -y skills add event4u-app/agent-config --skill override-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.8 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it

Override Skill

When to use

Use when creating or managing project-level overrides for shared skills, rules, commands, or guidelines — customizing .augment/ content without modifying originals.

Do NOT use when:

  • Changing shared content that should affect all projects (edit src/ directly)
  • Creating new skills from scratch (use skill-writing skill)

Purpose

The .augment/ directory is delivered as a Composer package and is read-only at project level. It contains shared skills, rules, commands, guidelines, and templates that work across all projects.

The agents/overrides/ directory is project-specific and lives in the project's own repository. It customizes shared behavior for a particular codebase without modifying the originals.

Critical rule: Never edit files in .augment/ to fix a project-specific need. Changes to .augment/ affect ALL projects. Use overrides instead.

Procedure: Create an override

Before creating an override, understand the original:

  1. Read the original from .augment/{type}/{name} — understand its purpose, structure, and behavior.
  2. Check for existing overrides in agents/overrides/{type}/ — avoid duplicates.
  3. Identify what needs changing — only override the specific behavior that differs for this project.

When loading any skill, rule, or command:

  1. Load the original from .augment/{type}/{name}
  2. Check for override in agents/overrides/{type}/{name}
  3. If override exists, read its Mode header:
    • extend — Apply the original first, then layer the override on top (additive)
    • replace — Ignore the original entirely, use only the override

Directory Structure

agents/overrides/
├── rules/           ← Override .augment/rules/*.md
│   └── .gitkeep
├── skills/          ← Override .augment/skills/*/SKILL.md
│   └── .gitkeep
├── commands/        ← Override .augment/commands/*.md
│   └── .gitkeep
├── guidelines/      ← Override .augment/guidelines/**/*.md
│   └── .gitkeep
└── templates/       ← Override .augment/templates/*.md
    └── .gitkeep

File Naming Convention

Override files must match the original filename exactly:

OriginalOverride
.augment/rules/php-coding.mdagents/overrides/rules/php-coding.md
.augment/skills/eloquent/SKILL.mdagents/overrides/skills/eloquent.md
.augment/commands/feature/plan.mdagents/overrides/commands/feature/plan.md
../../../docs/guidelines/php/controllers.mdagents/overrides/guidelines/php-controllers.md
.augment/templates/roadmaps.mdagents/overrides/templates/roadmaps.md

Skills are flattened: the original lives in a directory (skills/{name}/SKILL.md), but the override is a single file (skills/{name}.md).

Guidelines are flattened with a prefix: docs/guidelines/php/controllers.md → guidelines/php-controllers.md.

Templates keep their original filename: templates/roadmaps.md → templates/roadmaps.md.

Override File Format

Every override file must have this header:

# Override: {Type} — {name}

> Override for `.augment/{path-to-original}`

---
**Mode:** `extend`
**Original:** `.augment/{path-to-original}`
---

Mode: extend

  • The original is loaded first
  • The override adds, modifies, or removes specific parts
  • Reference original sections by heading name
  • Only write what changes — everything else stays as-is

Mode: replace

  • The original is completely ignored
  • The override is the sole source of truth
  • Must be self-contained and complete

When to Create Overrides

SituationAction
Shared skill doesn't match project conventionsextend — add project-specific rules
Shared command needs extra steps for this projectextend — inject additional steps
Shared rule is too strict/lenient for this projectextend — adjust specific rules
Shared guideline misses project-specific patternsextend — add examples or sections
Shared template needs extra fields for this projectextend — add project-specific fields
Shared skill is completely wrong for this projectreplace — write from scratch
Project needs behavior not in any shared skillCreate a new skill in .augment/skills/ instead

When NOT to Create Overrides

  • Don't override to fix bugs in the shared package — fix the original in the .augment/ package repo instead
  • Don't override for temporary changes — use branch-specific notes instead
  • Don't create empty overrides — only create when there's actual content
  • Don't duplicate the original — extend mode should only contain the delta

Checking for Overrides (Agent Behavior)

Before executing any skill, rule, or command, agents must:

  1. Note the original path (e.g., .augment/skills/eloquent/SKILL.md)
  2. Check if agents/overrides/skills/eloquent.md exists
  3. If it exists, read the Mode header
  4. Apply accordingly:
    • extend → Load original, then apply override additions/changes
    • replace → Skip original, use override only

Templates

Override templates are in .augment/templates/overrides/:

TemplateFor
rule.mdOverriding a rule
skill.mdOverriding a skill
command.mdOverriding a command
guideline.mdOverriding a guideline
template.mdOverriding a template

Related

  • Commands: /override-create, /override-manage
  • Skill: agent-docs-writing (documentation hierarchy)
  • Templates: .augment/templates/overrides/

Validate

  • Verify the override file exists at the correct path in agents/overrides/.
  • Confirm the override actually takes effect (test the behavior it modifies).
  • Check that the original in .augment/ is not modified.

Output format

  1. Override file in agents/overrides/ matching the original's structure
  2. Summary of what was overridden and why

Gotcha

  • Overrides are invisible to other projects — only the current project sees them.
  • Replace mode discards the original entirely — use extend mode unless you need a full rewrite.
  • If the override stops working after a package update, the original's structure likely changed.

Do NOT

  • Do NOT create overrides for things that should be changed in the original.
  • Do NOT use replace mode when extend mode is sufficient.

Auto-trigger keywords

  • override
  • project override
  • extend skill
  • replace skill

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.