go · laguagu — Claude Code skill: what it does, how to install
go — a Claude Code skill that launches the web app and verifies UI changes in a real browser. Smoke tests functional behavior, console errors, and HTTP failures.
MIT 112 installs ★ 74 updated 2026-11-14
npx skills add laguagu/claude-code-nextjs-skills --skill go -a claude-codeWhat go does
The skill starts the local development server according to project documentation, launches a browser, and confirms recent interface updates. It tests actual user interactions rather than static rendering, checking that searches return relevant data. It also monitors JavaScript console logs and watches for failed network requests with 4xx or 5xx codes.
Login screens do not halt execution. The skill prefers a browser profile with an active session to preserve SSO, OAuth, and MFA states. When test accounts are required, runner scripts like Playwright read credentials directly from environment variables. Exposing .env credentials in chat or tool parameters is blocked.
When interface errors occur, the agent applies fixes and re-verifies. If an issue survives two consecutive fix attempts, it changes strategy or hands off to a secondary model.
What it helps with
- run smoke tests on web UI changes in a real browser
- launch local servers directly from project scripts
- catch browser console errors and failed HTTP requests
- verify authenticated flows without leaking secrets into prompts
Example prompts for the agent
- Check recent changes in browser and make sure it works
- /go
- Update the navigation drawer and verify it works on mobile
How to install go
1Skills CLI (Vercel)
npx skills add laguagu/claude-code-nextjs-skills --skill go -a claude-code2Manually: put the files in place
~/.claude/skills/go/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/go/
1Skills CLI (Vercel)
npx skills add laguagu/claude-code-nextjs-skills --skill go -a codex2Manually: put the files in place
.agents/skills/go/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add laguagu/claude-code-nextjs-skills --skill go -a cursor2Manually: put the files in place
.cursor/skills/go/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install laguagu/claude-code-nextjs-skills skills/go2Manually: put the files in place
.github/skills/go/SKILL.md1Skills CLI (Vercel)
npx skills add laguagu/claude-code-nextjs-skills --skill go -a gemini-cli2Platform CLI
gemini skills install https://github.com/laguagu/claude-code-nextjs-skills --path skills/goManually: put the files in place
.devin/skills/go/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add laguagu/claude-code-nextjs-skills --skill go -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about go
How to install go in Claude Code?
Run npx skills add laguagu/claude-code-nextjs-skills --skill go -a claude-code in your terminal. You can also place the skill file in ~/.claude/skills/go/SKILL.md.
What does the go skill do?
It launches your web application, opens it in a browser, and tests recent changes. It verifies interactive behavior, tracks console errors, and monitors network responses.
How does go handle protected routes?
It checks existing browser sessions that already passed SSO or OAuth logins. For test environments, automation scripts read credentials from environment variables without printing them into chat.
Source text
SKILL.md · MIT
--- name: go description: Opens the app in a browser, starting it first if it is not running, and verifies that recent UI changes actually work. Use for a quick browser smoke test of recent web work — "go", "test in browser", "check in browser", "make sure it works", "verify it works", "did it work", "works on mobile" — including when the user appends "...and make sure it works" to a UI request. For a UI/UX review or polish pass of the running app, use a UI-review skill such as go-ui when it is installed; for a code audit against the Web Interface Guidelines, use web-design-guidelines. For a web UI, this skill does the check even where Claude Code's run or verify skill is installed; for a CLI, TUI or desktop app, use one of those. --- # /go — Browser check Verify the work in a real browser instead of trusting that it compiles. If the app is not running, start it the way the project documents (README, package scripts or the project's own launch skill). Easy to miss: - **Functional result** — the page does what was intended, not just renders. A search for "X" shows results about X. - **Console and network** — JS errors and failed requests (4xx/5xx) break things silently. A login wall is not a reason to stop. Prefer a browser where the user is already signed in; that also covers SSO, OAuth and MFA. Otherwise use a test account from the project's seed, fixture or example config, or the user's secrets manager. Do not open, print or search an env file for credentials: if a test login exists only there, load it inside the script that signs in (for example a Playwright script reading process.env), never through chat or tool arguments. On a deployed site a signed-in session is the user's real account, so check without changing data. If something is broken, fix and verify again. When the same issue survives two fixes, change approach or get a second reader (another model or agent, when one is available); ask for direction only if it still fails.
© laguagu · MIT · laguagu/claude-code-nextjs-skills
Similar skills
All skills for Testing and QA →go by other authors comes first.