Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Skills in this repository
garrytan/gstack - Page 2
SkillsMP has collected 64 skills from garrytan/gstack. Open a skill to review its source and details.
garrytan/gstackShowing 24 of 64 collected skills.
Read-only queue dashboard for workspace-aware ship. (gstack)
Manage project learnings.
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). (gstack)
Report browser/API/CLI/job/worker/webhook bugs. (gstack)
Weekly engineering retrospective. (gstack)
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)
Keep gbrain current with this repo's code and refresh agent search guidance in CLAUDE.md. (gstack)
Cross-model benchmark for gstack skills. (gstack)
Turn an English description (or mermaid source) into a diagram triplet: the source, an editable .excalidraw file you can open on excalidraw.com, and rendered SVG + PNG. (gstack)
Turn any markdown file into a publication-quality PDF. (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)
Find worthwhile shared-code extractions in recent work. (gstack)
Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)
Scrape the Hacker News front page (titles, points, comment counts).
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.
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.