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.

references/command-form-and-location.md

View on GitHub
# Command Form and Location

## Choose the Narrowest Command Surface

- Before choosing a repository location, load `fish-shell-scripting` and apply its wrapper selection and execution boundary policies.
- After that check, use `home/.config/fish/functions/<command-name>.fish` by default for a command used only through Fish.
- When an executable entrypoint becomes an autoloaded Fish function, place the function in its matching file without a hashbang or executable bit. Preserve its documentation and observable contract, and migrate every caller before removing the entrypoint.
- When the selected execution boundary is the current Fish process, the resulting function placement takes precedence over a desired `domfiles` or Git subcommand spelling.
- Add `home/.local/bin/<command-name>` only when the selected execution boundary requires an executable, including invocation by a non-Fish caller or before Fish is available.
- Put a `domfiles` subcommand at `home/.local/bin/domfiles-<command-name>`. For a Git subcommand, follow [Git helper form](#choose-git-helper-form) before using `home/.local/bin/git-<command-name>`.

## Choose Git Helper Form

- Before adding or reviewing a `home/.local/bin/git-*` entrypoint, inspect `home/.config/git/config` and determine whether a plain Git alias preserves the required behavior.
- Prefer a plain Git alias when the helper invokes one Git subcommand with fixed options and relies on Git’s normal argument forwarding.
- Keep a script when the behavior requires shell control flow, dynamic values, safety checks, external commands, or shared `domlib` behavior.
- If a Git alias would require the `!` shell command form, implement it as a `home/.local/bin/git-*` script instead. Never define shell commands inside `home/.config/git/config` aliases.
- Don’t retain a script solely for custom argument count validation unless strict arity is required behavior.
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: 471kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall