All ideasMore in Work

I told the AI not to sign my commits. It signed 25 of them in a row.

Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.

This one went wrong. Read what happened so you don’t hit the same problem.

How it works

  1. Checked his own configuration for twenty minutes and proved he had not broken it, Found the same signing in two public projects and then a private one with 25 signed commits in a row, Counted 40 signed commits across three days, from two different models, Asked the agent what happened and checked the changelog, where the fix was already claimed

Why it’s worth knowing

The instruction and the note saying his instruction outranked the default were both in context. The default still won, 25 times in a row, without him noticing once.

Where it’s from

Summarized from a public post on albertoarena.it. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.