Skip to content

porada/domfiles / .agents/skills/shell-integration

shell-integration

Verified

Use this skill whenever the resolved task scope includes shell code—including `domlib`, Fish configuration, `home/.local/bin` scripts, and `.hooks`—or adds or reconsiders a command entrypoint in this repository, including whether a Git helper should be a plain alias or a `home/.local/bin/git-*` script. Do not use it merely because the task runs terminal commands.

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.

Manage Cache Variables

When a function stores a result in a global variable to avoid recomputing it on later calls, prefix the variable name with __domfiles_cache_. Treat that variable as private to its owning function. Callers must use the function’s output or exit status rather than read, query, or modify its cache.

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, select checks and interpret their results under its read-only audit boundary.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall