agentleFS
bmcszkbmcszk/agent-skills/skills/shell-startup-files/SKILL.md

shell-startup-files

Skill2 starsChanged 18 days agoMITView on GitHub

Use when editing zsh or bash startup files, placing env vars, or debugging why a shell session, cron job, or ssh command missed its environment - sourcing matrix, guards, and per-host branching.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before shipping a startup-file change, run: bash -n and zsh -n (syntax), env -i bash (cron simulation), bash -lc 'echo $PATH' (login PATH …

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shell startup files

The sourcing matrix

  • zsh non-interactive reads .zshenv ONLY.
  • bash non-interactive reads NOTHING.
  • A non-login ssh bash command reads .bashrc: env loading goes ABOVE the interactivity guard or ssh host command runs without the environment.

environment.d confs are parsed literally

systemd environment.d confs are parsed literally while shell eval-loops expand: no variable expansion and no command substitution inside a conf, or the two consumers silently diverge on the same variable. One wrong conf feeds a shell $HOME and a systemd unit the literal string $HOME.

Daemons spawned from rc files

An rc-spawned daemon dies with the shell unless it gets its own session: launch with setsid. A new env.d conf is invisible to the running user manager until systemctl import-environment (or a daemon-restart) picks it up.

The interactivity guard

zsh -i with no controlling tty still sets -o interactive, so an [[ -o interactive ]] guard alone is not a tty check: test -t 0 AND -t 1, and make the guard the first executable line - anything above it runs in every non-interactive consumer too.

Per-host branching

Branch per host on runtime guards, never on parsed files: $HOSTNAME in bash, $HOST in zsh. The lowercase $hostname exists in neither by default and is silently empty, so a lowercase branch matches every host at once.

Test battery for rc edits

Before shipping a startup-file change, run: bash -n and zsh -n (syntax), env -i bash (cron simulation), bash -lc 'echo $PATH' (login PATH reset check), and zsh -ic 'alias' asserts (interactive aliases present).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.