> 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 4 days ago | parent [-]

Does this mean it's only useful for issue fixes?

▲

regularfry 4 days ago | parent [-]

A feature is just an issue. The issue is that the feature isn't complete yet.

▲

afro88 3 days ago | parent [-]

> 2. Create a script to reproduce the issue

Surely that would send it a bit off the rails to implement a feature?

▲

regularfry 3 days ago | parent [-]

Sounds like an acceptance test to me!

	▲	afro88 3 days ago \| parent [-]
		True. I guess I should actually try it out :)