classicpsy

Thanks for the pointer. For now I’ve fixed the issue. Your reply made me go through the hook script solution more carefully, and I’m exploring it now.

Now it is convincing. But the same approach a week ago frustrated me. The problem was some guy in office wrote the logs, and it was somehow logging success even though it was going in the catch block due to an error. But the claude was convinced that the logs were right and even though i was telling it not to trust the logs and listing the exact thing to fix, it did the opposite and in the end i had to do it manually along with fixing the logger. Nevermind, your approach is reliable and will surely work when the logs are fine. Thanks

Mate I still didn't understand that.

stop hook forces the claude to run the existing tests. Fine if claude added a new feature but didn't created a test for it. It will wait for it to perform that action. Fine. We can adjust the complexitiy of hook scripts. That's ok.

Tell me if I'm wrong, I am understanding it more like a compiler like if the syntax is ok, just pass. Similarly here, if the test were ran, it will look for a marker file in /tmp, it found it, and pass.

I did not understood the part of tests. Maybe my question is more clear now.

> We're building feature X. - You might need `a`, `b`, `c`. (any libraries, url documentation etc) - The requirements are: - x - y - z

So, you are saying we have to start every conversation for an existing project with this context? pointing to the particular feature detail we are targeting?

Looks an interesting approach.

So, the tests being written are based on what? on user input or to test the changes it made according to claude's analogy?

If it is the latter, it can be the same problem of forcing its analogy. In this case by validating it

That sounds relatable, but there are ways through which we can avoid being lazy. As for myself, I occasionally try to debug and fix the code myself instead of relying on coding tools. That doesn't give superhuman feeling like writing a whole project by hand, but still that helps.

Can't say fortunately or unfortunately, but we have no other choice but to keep up this way.

I tried it. Looks great. Just few refinements from my side.

- Undo is not working. If you applied something it will be done. I had to reupload the pdf to again make the changes.

- I tried the text editing, it is having a defualt font family of `helvetica` and is automatically applied to the selected text once clicked and there is no way to undo or fix it.