MicKillah

My doubt in the factualness of this claim is too high to allow me to be interested at all. Especially with how bad my Claude Code experience has gotten in the past weeks. I thought it was me until I started reading other people's accounts of how it seems to have gotten "lazy" and "dumber" since around February. If they have such a capable aka dangerous model, how is no residual benefit showing up in the currently "in the wild" models? I know my anecdote is not proof of decline but I can only speak from my own experience(s).

Welp, I just might get flagged by your method then. I lurk extensively on this site. I haven’t figured out how to “fit in”.

That would definitely be helpful, but the headline hit a painful spot for me and I went in! You’re right tho! I was in my feelins. I still am. lol

This comes up from time to time and although my experience is anecdotal, I see clear degradation of output when I run heavy loads (100s of batched/chunked requests, via an automated pipeline) and sometimes the difference in quality is absolutely laughable in how poor it is. This gets worse for me as I get closer to my (hourly, weekly) limits. I am Claude Max subscriber. There’s some shady stuff going on in the background, for sure, from my perspective and experience during my year or so of intense usage.

I can definitely vouch for that being the case, for me.

I want to say that I am surprised but that would be an outright lie.

However, I did do some prompt "engineering" alongside using your literal request. I definitely should make it clear that I didn't only use your request verbatim but I augmented it a bit with some additional prompting cues.

I am not sure how you may have gone about it but I was able to get this script, from ChatGPT4:

  #!/bin/bash

# Check if a git repository if [ ! -d .git ]; then echo "This directory is not a git repository." exit 1 fi

# Filename for the output output_file="git_diff_searchable.txt"

# Empty the output file or create it if it doesn't exist > "$output_file"

# Process git diff output git diff --unified=0 | while read line; do # Check for filename line if [[ $line =~ ^diff ]]; then filename=$(echo $line | sed 's/diff --git a\/\(.\) b\/./\1/') elif [[ $line =~ ^@@ ]]; then # Extract line numbers line_numbers=$(echo $line | sed -E 's/@@ -[0-9]+(,[0-9]+)? \+([0-9]+)(,[0-9]+)? @@./\2/') else # Write filename and line number to the output file echo "$filename:$line_numbers: $line" >> "$output_file" fi done

echo "Output saved to $output_file"

I then ran the following egrep [corrected to egrep, after mistakenly putting that I used gawk] command egrep -e 'agent.rs:[0-9]{1,}' git_diff_searchable.txt* to see the results. Everything worked as I expected.

Now, I don't claim that this is what you intended to achieve but I prompted it with the context of what you asked: Write a script that converts git-diff output to a file that can be easily grepped by filename and linenumber.