setup-global-config

Installs and verifies byte-identical global agent guidelines for Claude Code and Codex.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill setup-global-config-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-global-config
Source: https://github.com/psw7205/skills/tree/main/skills/setup-global-config
Command: npx skills add https://github.com/psw7205/skills --skill setup-global-config-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping shared team-wide agent rules consistent across Claude Code and Codex is error-prone: files drift, manual edits diverge, and overwriting a user's existing global config can silently destroy their customizations. This Skill installs a canonical tool-agnostic guideline file to both agents byte-identically, with backup protection and verification. ## Core Features & Use Cases - Byte-identical installation: Copies the canonical references/global-config.md to ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md, verifying with cmp -s so newline or encoding differences never slip through. - Safe overwrite with backup: When an existing target differs, it summarizes the diff, asks for approval, and creates a timestamped .bak copy before replacing anything. - Safe uninstall: Restores a prior backup or deletes the file only when the target still matches canonical; user-modified files are reported as unresolved instead of deleted. - Use Case: A team lead publishes updated shared agent principles and asks the AI to roll them out on a teammate's machine; the Skill installs to both agents, backs up the old configs, and confirms byte-level equality. ## Quick Start Install the global config for Claude Code and Codex, backing up any existing files first.

Frequently Asked Questions about setup-global-config

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

FAQPage Schema
How do I install a shared CLAUDE.md and AGENTS.md global config?▼

Copy the canonical guideline file to ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md, then verify each target with cmp -s against the source. Back up any existing file to a timestamped .bak path before overwriting.

How to keep Claude Code and Codex global instructions in sync?▼

Maintain a single canonical markdown file and install it byte-identically to both agents rather than editing each file separately. Verify with cmp after every install, since diff can miss newline or encoding differences.

Does changing ~/.claude/CLAUDE.md affect the current session?▼

No. Global instruction files are loaded at session start, so changes only apply to new sessions. Start a fresh Claude Code or Codex session to confirm the updated rules are active.

What happens if my existing global config differs from the canonical file?▼

The install summarizes the differences and asks for approval before overwriting, then creates a timestamped backup with cp -p. During uninstall, a modified target is reported as unresolved instead of being deleted.

Why use cmp instead of diff to verify config installation?▼

cmp performs a byte-level comparison that catches newline and encoding differences a visual diff can miss. An exit status of 0 from cmp -s is the definitive check that the installed file matches the canonical source.