172
17

It ensures that the agent does a good job

1mon 5d ago by lemmy.world/u/fleck in programmer_humor@programming.dev

cross-posted from: https://lemmy.world/post/46800674

Image Text:

Github overview of a pull request for the file AGENTS.md.

Comments regarding line "# Repository Guidelines" in the file:

zanieb: "What's the point of this title? Seems like wasted tokens?"

zanieb: "(certainly inconsequential in the big scheme, but I don't see it adding value)"

charliemarsh: "It ensures that the agent does a good job."

Everyone knows you have to tell it "don't make mistakes".

"DO NOT HALLUCINATE"

Ahh, the "git gud" gamer hack also applies to sloperations? Good to know!

I actually stole that one from Apple

git config —global alias.gud “reset —hard @{upstream}”

You are a monster. Nice work!

Ah, went and checked my work laptop this morning. It’s actually set to: !”git reset —hard HEAD && git clean -fdx

git it is the one that’s set to upstream.

I also have git some: add -p, git away: checkout -p, git out: !”git merge —abort 2> /dev/null || git rebase —abort 2> /dev/null #”

And some complicated ones I’m not gonna type on my phone:

  • git on <foo> where foo is either “it”, in which case I use the appropriate main/master/develop branch and rebase on it; or foo is “up” in which case I do a pull —rebase and play a short audio clip of Get On Up; or foo is a nonexistent branch, in which case I massage the requested branch name to adhere to some conventions and then make a new branch and set the remote tracking branch
  • git with <foo> where the same “it” logic applies but it’s a merge; or foo is a commit SHA and it gets cherry-picked
  • git up is just a pull but it plays a short audio clip of Get On Up
  • I think I had a git rekt at one point, but I think it just did the same as git gud so I deleted it
git config --global alias.lsd '!f(){ p(){ awk '\''BEGIN{srand()}{a[NR]=$0}END{print a[int(rand()*NR)+1]}'\''; }; git reset --hard -q; git clean -fdq; if [ "$(awk '\''BEGIN{srand();print int(rand()*2)}'\'')" = 0 ]; then c=$(git rev-list --first-parent HEAD|sed "$d"|p); git reset --hard "$(git rev-parse "$c^")"; else c=$(git rev-list --all|grep -v "^$(git rev-parse HEAD)$"|p); git reset --hard "$(git commit-tree "$c^{tree}" -p HEAD -C "$c")"; fi; }; f'

You're welcome.

How many "do not hallucinates" does it take until the "memory window" forgets it's supposed to not hallucinate and then hallucinate?

Technically, nowadays, the system prompt is sent back with every user prompt, but I'm not convinced that was the case in 2024 😅

Do a good job

Sorted.

Be GOD.

Nothing can beat that!

That's a very good point you made!

that's just good form, regardless of who's reading the md

  • MD041 - First line in a file should be a top-level heading
  • MD002 - First header should be a h1 header
  • MD025 - Multiple top level headers in the same document

that whole line is 3 tokens btw, they're wasting more time and energy just discussing that

So now we learned how to make simple guidelines / docs

Without this, we wouldn't be sure the agent does a good job!

damn, Charlie really fell off