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

    • circuitfarmer@lemmy.world
      3·
      2 hours ago

      There are a shockingly high number of people who believe this kind of thing genuinely affects output from LLMs.

      I think the reason is simple: if you ask the LLM, it’ll tell you it’s a good idea.

            • kibiz0r@midwest.socialEnglish
              1·
              40 minutes ago

              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