Skill

chome-pattern

Use when a Bash command references ~/.claude/ and fails with "path not found" or "No such file or directory" in multi-account setups. Use when writing rm -rf for team or task directories, when CLAUDE_CONFIG_DIR is set to a custom path and SDK auto-resolution is unavailable, or when auditing commands for hardcoded ~/.claude/ paths. Failure scenario: rm -rf ~/.claude/teams/... silently targets wrong directory when CLAUDE_CONFIG_DIR is set. Keywords: CLAUDE_CONFIG_DIR, CHOME, ~/.claude, multi-account, config directory, path not found, team cleanup, hardcoded path. <example> Context: A command needs to rm-rf team directories after cleanup. user: "Add cleanup logic for team dirs" assistant: "I'll use the CHOME pattern for the rm-rf call — SDK calls like Read() auto-resolve, but Bash commands need explicit CHOME." <commentary>Load chome-pattern skill for correct Bash path resolution.</commentary> </example> <example> Context: Auditing a new command for hardcoded ~/.claude/ references. user: "Check if this command works with custom config dirs" assistant: "I'll classify each ~/.claude/ reference as SDK (safe) or Bash (needs CHOME)..." <commentary>CHOME skill provides the classification framework.</commentary> </example>

npx claudepluginhub vinhnxv/rune --plugin rune

Tool Access

This skill is limited to using the following tools:

ReadGlobGrep

Preview

Claude Code supports custom config directories via `CLAUDE_CONFIG_DIR` environment variable. Users with multiple accounts (work/personal) set this to different paths:

Supporting Assets

references/canonical-patterns.md

SKILL.md

Similar Skills

user-config-management

Manages Claude Code user configs (~/.claude/, ~/.claude.json): storage cleanup, backup/restore, reset with MCP preservation, history/plans/sessions/stats, health audits.

4 files5 tools

claude-ecosystem

claude-code-bash-patterns

Provides Claude Code bash patterns for PreToolUse hooks, command chaining, CLI orchestration, git workflows, custom commands, and handling bash permissions, failures, security guards.

12 files

claude-code-bash-patterns

health

Audits Claude Code project configuration for drift and collaboration issues across six layers (CLAUDE.md, rules, skills, hooks, subagents, verifiers), tiered by project complexity.

toolbox

Stats

Parent Repo Stars1

Parent Repo Forks1

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

CHOME Pattern — Multi-Account Config Directory Resolution

Problem

Claude Code supports custom config directories via CLAUDE_CONFIG_DIR environment variable. Users with multiple accounts (work/personal) set this to different paths:

# Default
~/.claude/

# Custom (work account)
CLAUDE_CONFIG_DIR=~/.claude-work

# Custom (personal)
CLAUDE_CONFIG_DIR=~/.claude-personal

When code hardcodes ~/.claude/, it breaks on custom setups — rm-rf deletes the wrong dir, find scans the wrong path, test checks the wrong location.

The Rule: SDK vs Bash

Specialized SDK calls — SAFE, auto-resolve internally

These tools manage config dirs internally and always resolve CLAUDE_CONFIG_DIR:

Tool	Example	Safe?
`TeamCreate()`	`TeamCreate({ team_name: "my-team" })`	Yes
`TeamDelete()`	`TeamDelete()`	Yes
`TaskList()`	`TaskList()`	Yes
`SendMessage()`	`SendMessage({ type: "message", ... })`	Yes

Generic file tools + Bash — MUST use CHOME

Read(), Write(), Glob() are generic file tools — they read/write the exact path you give them. Bash() executes shell commands literally. Neither auto-resolves CLAUDE_CONFIG_DIR:

Tool	Example	Safe?
`Read(\`~/.claude/...`)`	Reads wrong dir if CLAUDE_CONFIG_DIR set	NO
`Write(\`~/.claude/...`)`	Writes wrong dir	NO
`Glob("~/.claude/...")`	Scans wrong dir	NO
`Bash("rm -rf ...")`	Deletes wrong dir	NO
`Bash("find ...")`	Scans wrong dir	NO
`Bash("test -d ...")`	Checks wrong dir	NO

Canonical Patterns

Three patterns for resolving CHOME: (1) inline for single Bash calls, (2) resolved variable for multiple calls, (3) documentation notation for human-readable docs. Each includes code examples for rm-rf, find, test -f, and test -d operations.

See canonical-patterns.md for full code examples of all 3 patterns.

Classification Checklist

When auditing a file for hardcoded ~/.claude/, classify each reference:

Context	Action
Inside `Bash(...)`	FIX — use CHOME pattern
Inside `Read(...)`	FIX — resolve CHOME first, pass `${CHOME}/teams/...`
Inside `Write(...)`	FIX — resolve CHOME first, pass `${CHOME}/...`
Inside `Glob(...)`	FIX — resolve CHOME first, pass `${CHOME}/...`
In `TeamCreate/TeamDelete/TaskList`	SAFE — specialized SDK, auto-resolves
In markdown table	OPTIONAL — add `(or $CLAUDE_CONFIG_DIR if set)` note
In YAML comment	SAFE — user docs, no code execution
In CHANGELOG	SAFE — historical record

Session Identity Triplet

CHOME resolves installation isolation (which Claude Code config dir). Two additional fields complete the session identity triplet for session isolation:

Field	Source	Isolation Layer
`config_dir`	`CHOME` (resolved `CLAUDE_CONFIG_DIR`)	Installation — different Claude Code configs
`owner_pid`	`$PPID` in Bash	Session — different sessions with same config
`session_id`	`CLAUDE_SESSION_ID` / `${CLAUDE_SESSION_ID}` in skills	Diagnostic — correlation across hooks and logs

All Rune state files must include all three fields. See protocols.md § Session Isolation Protocol for the full ownership verification matrix.

Security: Always Quote CHOME

The CHOME variable MUST be double-quoted in all Bash contexts to prevent word splitting:

// CORRECT — quoted
Bash(`rm -rf "$CHOME/teams/${name}/"`)

// WRONG — unquoted, breaks on paths with spaces
Bash(`rm -rf $CHOME/teams/${name}/`)

Anti-Patterns

exists() with bare path

// WRONG — exists() is not an SDK call, it's a pseudocode helper
if (exists(`~/.claude/teams/${name}/`)) { ... }

// CORRECT — use Bash test with CHOME
const result = Bash(`CHOME="\${CLAUDE_CONFIG_DIR:-$HOME/.claude}" && test -d "$CHOME/teams/${name}/" && echo "exists"`)
if (result.trim() === "exists") { ... }

Read/Bash with bare ~/.claude/ path

// WRONG — Read is a generic file tool, does NOT auto-resolve CLAUDE_CONFIG_DIR
const config = Read(`~/.claude/teams/${name}/config.json`)

// WRONG — Bash does NOT auto-resolve either
Bash(`rm -rf ~/.claude/teams/${name}/`)  // BUG: wrong dir on custom setups

// CORRECT — resolve CHOME once, use for both Read and Bash
const CHOME = Bash(`echo "\${CLAUDE_CONFIG_DIR:-$HOME/.claude}"`).trim()
const config = Read(`${CHOME}/teams/${name}/config.json`)
Bash(`rm -rf "${CHOME}/teams/${name}/"`)

Grep Audit Commands

To find all ~/.claude/ references in a project:

# All references
rg '~/\.claude/' plugins/rune/

# Only Bash-context (dangerous)
rg 'Bash\(.*~/\.claude/' plugins/rune/

# rm-rf/find/test/ls in shell context
rg 'rm -rf ~/\.claude/|find ~/\.claude/|test -d ~/\.claude/|ls ~/\.claude/' plugins/rune/

# exists() with bare path (pseudocode anti-pattern)
rg 'exists\(.*~/\.claude/' plugins/rune/