CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-02 11:45:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

feat: add browse access to /debug for visual verification

Browse Source 
Debug skill can now use the browse binary to visually reproduce bugs,
take screenshots as evidence, and verify fixes. This makes /debug
effective for web app bugs when spawned as a sub-agent from /qa.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-18 11:08:10 -07:00
parent 8914a0fdce
commit 901358c2f1
2 changed files with 53 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
debug/SKILL.md
+35
View File
@@ -145,6 +145,25 @@ ATTEMPTED: [what you tried]
RECOMMENDATION: [what the user should do next]
```
## SETUP (run this check BEFORE any browse command)
```bash
_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
B=""
[ -n "$_ROOT" ] && [ -x "$_ROOT/.claude/skills/gstack/browse/dist/browse" ] && B="$_ROOT/.claude/skills/gstack/browse/dist/browse"
[ -z "$B" ] && B=~/.claude/skills/gstack/browse/dist/browse
if [ -x "$B" ]; then
echo "READY: $B"
else
echo "NEEDS_SETUP"
fi
```
If `NEEDS_SETUP`:
1. Tell the user: "gstack browse needs a one-time build (~10 seconds). OK to proceed?" Then STOP and wait.
2. Run: `cd <SKILL_DIR> && ./setup`
3. If `bun` is not installed: `curl -fsSL https://bun.sh/install | bash`
# Systematic Debugging
## Iron Law
@@ -171,6 +190,14 @@ Gather context before forming any hypothesis.
4. **Reproduce:** Can you trigger the bug deterministically? If not, gather more evidence before proceeding.
5. **Visual reproduction (if browser-testable bug):** Use the browse binary to reproduce the bug:
```bash
$B goto <affected-url>
$B screenshot screenshots/debug-ISSUE-NNN-repro.png
$B console --errors
```
Compare what you see against the reported symptom. If the bug is not reproducible visually, that's useful evidence too — the root cause may be in data flow, not rendering.
Output: **"Root cause hypothesis: ..."** — a specific, testable claim about what is wrong and why.
---
@@ -249,6 +276,14 @@ Once root cause is confirmed:
Run the test suite and paste the output.
**Visual verification (if browser-testable bug):**
```bash
$B goto <affected-url>
$B screenshot screenshots/debug-ISSUE-NNN-fixed.png
$B console --errors
```
Compare against the original reproduction screenshot. The bug should no longer be present.
Output a structured debug report:
```
DEBUG REPORT
debug/SKILL.md.tmpl
+18
View File
@@ -16,6 +16,8 @@ allowed-tools:
{{PREAMBLE}}
{{BROWSE_SETUP}}
# Systematic Debugging
## Iron Law
@@ -42,6 +44,14 @@ Gather context before forming any hypothesis.
4. **Reproduce:** Can you trigger the bug deterministically? If not, gather more evidence before proceeding.
5. **Visual reproduction (if browser-testable bug):** Use the browse binary to reproduce the bug:
```bash
$B goto <affected-url>
$B screenshot screenshots/debug-ISSUE-NNN-repro.png
$B console --errors
```
Compare what you see against the reported symptom. If the bug is not reproducible visually, that's useful evidence too — the root cause may be in data flow, not rendering.
Output: **"Root cause hypothesis: ..."** — a specific, testable claim about what is wrong and why.
---
@@ -120,6 +130,14 @@ Once root cause is confirmed:
Run the test suite and paste the output.
**Visual verification (if browser-testable bug):**
```bash
$B goto <affected-url>
$B screenshot screenshots/debug-ISSUE-NNN-fixed.png
$B console --errors
```
Compare against the original reproduction screenshot. The bug should no longer be present.
Output a structured debug report:
```
DEBUG REPORT