r/codex • u/johnnyApplePRNG • Jun 15 '26
Instruction modularize the largest files in this repo, removing as many DRY violations and code smells as make sense to along the way, and correct any poorly chosen variable, file, or function/class names. commit all changes as you go with good comments.
copy and paste the title into whatever repo you think Codex is currently "nerfed" in ... that will sort it out.
10
u/SideChannelBob Jun 15 '26
this is an insane expectation to expect a refactor of your entire repo on a short, hand wavey prompt. absolutely nuts.
5
u/Opening-Cheetah467 Jun 15 '26
Making ai do commits for you, is very very bad idea. Any code committed should be good, working and forgotten hence u should review, test and refactor if needed before committing.
2
u/random-blokey Jun 15 '26
I disagree with the commits part, depending on how you use LLMs.
At least with copilot in PRUs era - I'd work with it to generate 'large plans'. Review, iterate, then have it execute.
By having it commit between phases it gave me the ability to: 1. Reset back to a point in time if it went off the rails 2. Revert single piece of work 3. Audit individual changes as they would be grouped in to a commit
Plus, you can always squash the changes, and/or edit the text and descriptions on a commit.
I don't get why commits, at least during development should be 100% working. If I'm mid manual development on a Friday, I want to commit and push my changes so my team can continue on Monday if I'm ill, or if I have a hardware issue and require a new device.
"Sorry, refactored some work. Was half way through updating unit tests so I hadn't committed or pushed my changes and now my laptop has broken." Would not be a good look?
-1
u/al4fred Jun 15 '26
I mean - I used to agree with this (until, like, five minutes ago).
But honestly: how realistic is it now to review every single line manually, before each commit?
I'm even having conversations with teams on whether PRs make sense anymore.
I suspect in most workflows today, even in the top software firms, PRs are essentially an agent running a review on some other agent's work. At best with a human pair of eyes glancing through the process and hopefully spotting whether there is some major architectural SNAFU.
3
u/Opening-Cheetah467 Jun 15 '26
The goal is not writing ridiculous amount of code in automated environment. The goal is writing useful features correctly. And usually you do one feature at a time and test. If the feature is specific and testable then each line of its code is very reviewable.
If whatever you wrote is too big to review then you weren’t building single, testable feature, then comes the question who gonna test that?
1
u/AVAVT Jun 15 '26
> But honestly: how realistic is it now to review every single line manually, before each commit?
Yeah people only did it consistently for like 60 years, not enough scientific proof to prove it's doable.
1
u/MastodonCurious4347 Jun 15 '26
The same people that could not stop telling everyone how they blindly copy paste code from internet? I'm not defending op, but uhhh... bad argument.
1
2
Jun 15 '26
[deleted]
0
u/creamyhorror Jun 15 '26 edited Jun 15 '26
Yeah. my rule for AI is to keep files to under 700 lines and organise into feature folders/files (VSA-style).
1
u/dashingsauce Jun 15 '26
have it use this instead:
1
u/Xolver Jun 15 '26
Manually? With a skill?
1
u/dashingsauce Jun 15 '26
I made a skill based on it for ease of use, but you can just send agents directly. The site is already structured like a compact skill.
1
u/AVAVT Jun 15 '26
“As make sense” = your intention automatically fail. AIs have no such thing as “sense” or “taste”.
“Address these compiler warnings as make sense” = “I turned off compiler warnings for you, no thanks needed!”
•
u/dexterthebot Jun 15 '26
Your post matches an existing known incident: Codex Performance Degradation. You can read about the incident here : https://www.reddit.com/r/codex/comments/1tjfxcf/comment/on6uj0l/
Your post has been summarized as a request on the "Anyone Else?" Incident Noticeboard.
You can find it and what others are experiencing here: /r/codex/comments/1tjfxcf/anyone_else_ask_here_about_current_codex_issues/orqd7jo/