gstack

Author	SHA1	Message	Date
rodri	94b64df593	When you present Claude Code with a bug, it tends to assume what the problem is and jump straight to implementation. Sometimes it will be wrong. It can take a lot of back and forth, and for each hypothesis Claude will make changes to the code that it won't undo after it eventually gets the solution right. /bugfix forces a disciplined workflow: reproduce the bug first, prove the root cause before writing any code, then fix it with a failing test as proof. No guessing, no leftover changes from wrong attempts. And after the fix, it closes the test gap that let the bug through in the first place.	2026-03-12 13:11:15 -03:00
Garry Tan	044c6d568e	v0.0.2 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-12 07:37:08 -07:00
morluto	a29743b056	fix: harden browse install and lifecycle checks (#4 ) Thanks @morluto	2026-03-12 07:35:20 -07:00
Garry Tan	3d901066cd	Initial release — gstack v0.0.1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-12 01:32:16 -07:00