3 ms·
> 1. Analyze the codebase by finding and reading relevant files 2. Create a script to reproduce the issue 3. Edit the source code to resolve the issue
by meander_water 1y ago
> 1. Analyze the codebase by finding and reading relevant files
2. Create a script to reproduce the issue
3. Edit the source code to resolve the issue
4. Verify your fix works by running your script again
5. Test edge cases to ensure your fix is robust
This prompt snippet from your instance template is quite useful. I use something like this for getting out of debug loops:
> Analyse the codebase and brainstorm a list of potential root causes for the issue, and rank them from most likely to least likely.
Then create scripts or add debug logging to confirm whether your hypothesis is correct. Rule out root causes from most likely to least by executing your scripts and observing the output in order of likelihood.
- afro88 1y agoDoes this mean it's only useful for issue fixes?
- regularfry 1y agoA feature is just an issue. The issue is that the feature isn't complete yet.
- afro88 1y ago> 2. Create a script to reproduce the issue Surely that would send it a bit off the rails to implement a feature?
- regularfry 1y agoSounds like an acceptance test to me!
- afro88 1y agoTrue. I guess I should actually try it out :)