Repository navigation
A docs-only change, and three things EGM caught #428
ccalabro
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I tried Google's Elephant-Goldfish Model on a docs-only change in a CLI I'm building to check repositories for engineering best practices. I needed
scan --targetscommand to show a JSON sample and a YAML sample, fortargets.jsonortargets.yml.I ran the session in Codex CLI and picked GPT-6 Luna because the task was very simple. It still caught three things I would have shipped:
scan --helpandCLI.mdcould drift apart. I asked it to address the risks. It updated the brief so both locations' examples are identical, and added a parity check to the acceptance criteria.AGENTS.mdsays to keep private review material out of the repo, and the reviewer picked that up from there. The plan changed to write to a temporary folder outside the repo.egm-drift-report. It found that the help and CLI.md never said commit values are compared exactly, even though the design required it. I added that note.I wrote up the full pass here: https://x.com/c_calabro/status/2120546834716254615
A LinkedIn copy is also here: https://www.linkedin.com/pulse/how-i-used-googles-elephant-goldfish-model-build-one-feature-calabro-10fff
All reactions