Domfiles Shell Integration

Use this skill as the canonical source for domfiles-specific shell integration, invariants, and validation.

For every Fish target, load fish-shell-scripting for portable language policy and workflow. For every POSIX shell target, load posix-shell-scripting. Apply this skill as the narrower domfiles layer when either language skill governs the same task.

Investigate Tasks

1. Classify each in-scope shell file from its hashbang and syntax rather than its extension alone, then apply fish-shell-scripting or posix-shell-scripting.
2. Evaluate home/.config/fish/functions/clone.fish against the Fish clone argument contract. Don’t report the absence of Git option parsing, option rejection, or reliable follow-up directory changes for unsupported option-bearing invocations.

For every non-Fish shell target and whenever the task touches domlib, a Fish __domfiles_* helper, shared $DOMFILES_* state, or command suppression, follow domlib Integration.

Check Supported Environment Compatibility

• Evaluate every in-scope domfiles shell script’s interpreter, external commands, options, PATH, architecture, and default-shell assumptions against the supported environment.
• Judge each requirement at its intended lifecycle stage—fresh bootstrap, synchronization, post-sync runtime, or development—and account for prerequisites that domfiles sync provisioned earlier.
• Place __is_ci and __domfiles_is_ci checks, including negations, last among predicates in compound conditions so CI detection doesn’t short-circuit the other checks. Preserve boolean grouping and keep CI-guarded actions conditional.
• Treat domfiles dependencies as the user-facing readiness check defined by dependency status labels. Add a row only for an established user-facing synchronization or runtime contract. Agent-only use or installation by synchronization alone doesn’t qualify a dependency.

Apply Domfiles Shell Wording Constraints

Use the applicable language skill for semantic requirements and composition with human-facing-writing. Apply these domfiles-specific constraints after that workflow:

• Avoid first-person and subjective wording.
• Omit final punctuation from script comments and user-facing strings passed to __print*.
• Treat standalone headings and status labels as labels rather than sentences. Allow sentence case or title case, and do not require imperative voice.
• Use sentence case imperative voice for action and section comments.

Choose Command Form and Location

Don’t report an existing command solely because another supported form could express it, except when Git helper form applies.

Before adding a command entrypoint or explicitly reconsidering an existing command’s form or location, follow Command Form and Location.

Before reviewing a home/.local/bin/git-* entrypoint, follow Git helper form.

Evaluate Duplication and Reuse

• Don’t report the language-specific home/.local/bin/domfiles-dev-lint-* entrypoints as duplication merely because each retains its own default scope and lint command. Shared discovery and execution belong in domlib. See development lint wrapper architecture for the rationale.
• Consolidate shell implementations when they duplicate a substantial, virtually identical behavior pipeline that must remain aligned.
• Don’t report __string_* helpers or equivalent inline string operations as reimplementations.

Apply Domfiles Fish Conventions

• Write unquoted command substitutions as (…) as an exception to fish-shell-scripting’s $(…) template. Use "$(…)" only inside double quotes, where (…) does not expand.

Apply Domfiles POSIX Conventions

• Allow argumentless echo to print a blank line as an exception to posix-shell-scripting’s printf requirement.
• Report find commands that place -maxdepth anywhere other than immediately after the search path.

Validate Changes

After editing, follow Validate Shell Changes for lint, formatting, and shell integration checks.

Validate Shell Audits, Diagnoses, and Reviews

Run the applicable language skill’s read-only validation and check integration contracts. When invoked through audit, preserve its ban on linters and formatters and use only the remaining permitted checks.