Report-only QA testing. (gstack)
Skills in this repository
garrytan/gstack - Page 2
SkillsMP has collected 61 skills from garrytan/gstack. Open a skill to review its source and details.
garrytan/gstackShowing 21 of 61 collected skills.
Systematically QA test a web application and fix bugs found. (gstack)
Weekly engineering retrospective. (gstack)
Pre-landing PR review. (gstack)
Pull data from a web page. (gstack)
Import cookies from your real Chromium browser into the headless browse session. (gstack)
Configure deployment settings for /land-and-deploy.
Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. (gstack)
Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack)
Turn vague intent into a precise, executable spec in five phases. (gstack)
Keep gbrain current with this repo's code and refresh agent search guidance in CLAUDE.md. (gstack)
Safety guardrails for destructive commands. (gstack)
Restrict file edits to a specific directory for the session. (gstack)
Full safety mode: destructive command warnings + directory-scoped edits. (gstack)
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped…
Fixture dispatcher with a mode table and forced-read references.
Clean fixture tool skill with no forced reads and no mode table.
Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)
Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.