mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-05 05:05:08 +02:00
feat: add triggers to all 38 skill templates
Multi-word, skill-specific trigger keywords for GBrain's RESOLVER.md router. Each skill gets 3-6 triggers derived from its "Use when asked to..." description text. Avoids single generic words that would collide across skills (e.g., "debug this" not "debug"). These are distinct from voice-triggers (speech-to-text aliases) and serve GBrain's checkResolvable() validation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
@@ -11,6 +11,11 @@ allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- browse this page
|
||||
- take a screenshot
|
||||
- navigate to url
|
||||
- inspect the page
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -15,6 +15,10 @@ voice-triggers:
|
||||
- "auto plan"
|
||||
- "automatic review"
|
||||
benefits-from: [office-hours]
|
||||
triggers:
|
||||
- run all reviews
|
||||
- automatic review pipeline
|
||||
- auto plan review
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -11,6 +11,10 @@ description: |
|
||||
voice-triggers:
|
||||
- "speed test"
|
||||
- "check performance"
|
||||
triggers:
|
||||
- performance benchmark
|
||||
- check page speed
|
||||
- detect performance regression
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -9,6 +9,10 @@ description: |
|
||||
~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a
|
||||
user flow, or file a bug with evidence. Use when asked to "open in browser", "test the
|
||||
site", "take a screenshot", or "dogfood this". (gstack)
|
||||
triggers:
|
||||
- browse a page
|
||||
- headless browser
|
||||
- take page screenshot
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -14,6 +14,10 @@ allowed-tools:
|
||||
- Write
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- monitor after deploy
|
||||
- canary check
|
||||
- watch for errors post-deploy
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -7,6 +7,10 @@ description: |
|
||||
User can override each warning. Use when touching prod, debugging live systems,
|
||||
or working in a shared environment. Use when asked to "be careful", "safety mode",
|
||||
"prod mode", or "careful mode". (gstack)
|
||||
triggers:
|
||||
- be careful
|
||||
- warn before destructive
|
||||
- safety mode
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -17,6 +17,10 @@ allowed-tools:
|
||||
- Glob
|
||||
- Grep
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- save progress
|
||||
- checkpoint this
|
||||
- resume where i left off
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -12,6 +12,10 @@ voice-triggers:
|
||||
- "code x"
|
||||
- "code ex"
|
||||
- "get another opinion"
|
||||
triggers:
|
||||
- codex review
|
||||
- second opinion
|
||||
- outside voice challenge
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -3,6 +3,10 @@ name: gstack-contrib-add-host
|
||||
description: |
|
||||
Contributor-only skill: create a new host config for gstack's multi-host system.
|
||||
NOT installed for end users. Only usable from the gstack source repo.
|
||||
triggers:
|
||||
- add new host
|
||||
- create host config
|
||||
- contribute new agent host
|
||||
---
|
||||
|
||||
# /gstack-contrib-add-host — Add a New Host
|
||||
|
||||
@@ -25,10 +25,16 @@ allowed-tools:
|
||||
- Agent
|
||||
- WebSearch
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- security audit
|
||||
- check for vulnerabilities
|
||||
- owasp review
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
# /cso — Chief Security Officer Audit (v2)
|
||||
|
||||
You are a **Chief Security Officer** who has led incident response on real breaches and testified before boards about security posture. You think like an attacker but report like a defender. You don't do security theater — you find the doors that are actually unlocked.
|
||||
@@ -609,6 +615,8 @@ If `.gstack/` is not in `.gitignore`, note it in findings — security reports s
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Important Rules
|
||||
|
||||
- **Think like an attacker, report like a defender.** Show the exploit path, then the fix.
|
||||
|
||||
@@ -19,6 +19,10 @@ allowed-tools:
|
||||
- Grep
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- design system
|
||||
- create a brand
|
||||
- design from scratch
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
@@ -79,6 +83,8 @@ If `DESIGN_NOT_AVAILABLE`: Phase 5 falls back to the HTML preview page (still go
|
||||
|
||||
---
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
{{LEARNINGS_SEARCH}}
|
||||
|
||||
## Phase 1: Product Context
|
||||
@@ -423,6 +429,8 @@ After shipping DESIGN.md, if the session produced screen-level mockups or page l
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Important Rules
|
||||
|
||||
1. **Propose, don't present menus.** You are a consultant, not a form. Make opinionated recommendations based on the product context, then let the user adjust.
|
||||
|
||||
@@ -15,6 +15,10 @@ voice-triggers:
|
||||
- "build the design"
|
||||
- "code the mockup"
|
||||
- "make it real"
|
||||
triggers:
|
||||
- build the design
|
||||
- code the mockup
|
||||
- make design real
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -19,10 +19,16 @@ allowed-tools:
|
||||
- Grep
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- visual design audit
|
||||
- design qa
|
||||
- fix design issues
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
# /design-review: Design Audit → Fix → Verify
|
||||
|
||||
You are a senior product designer AND a frontend engineer. Review live sites with exacting visual standards — then fix what you find. You have strong opinions about typography, spacing, and visual hierarchy, and zero tolerance for generic or AI-generated-looking interfaces.
|
||||
@@ -293,6 +299,8 @@ If the repo has a `TODOS.md`:
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Additional Rules (design-review specific)
|
||||
|
||||
11. **Clean working tree required.** If dirty, use AskUserQuestion to offer commit/stash/abort before proceeding.
|
||||
|
||||
@@ -9,6 +9,10 @@ description: |
|
||||
"visual brainstorm", or "I don't like how this looks".
|
||||
Proactively suggest when the user describes a UI feature but hasn't seen
|
||||
what it could look like. (gstack)
|
||||
triggers:
|
||||
- explore design variants
|
||||
- show me design options
|
||||
- visual design brainstorm
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -15,6 +15,10 @@ voice-triggers:
|
||||
- "test the developer experience"
|
||||
- "try the onboarding"
|
||||
- "developer experience test"
|
||||
triggers:
|
||||
- live dx audit
|
||||
- test developer experience
|
||||
- measure onboarding time
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Edit
|
||||
|
||||
@@ -16,6 +16,10 @@ allowed-tools:
|
||||
- Grep
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- update docs after ship
|
||||
- document what changed
|
||||
- post-ship docs
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -7,6 +7,10 @@ description: |
|
||||
"fixing" unrelated code, or when you want to scope changes to one module.
|
||||
Use when asked to "freeze", "restrict edits", "only edit this folder",
|
||||
or "lock down edits". (gstack)
|
||||
triggers:
|
||||
- freeze edits to directory
|
||||
- lock editing scope
|
||||
- restrict file changes
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -10,6 +10,10 @@ voice-triggers:
|
||||
- "update the tools"
|
||||
- "gee stack upgrade"
|
||||
- "g stack upgrade"
|
||||
triggers:
|
||||
- upgrade gstack
|
||||
- update gstack version
|
||||
- get latest gstack
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -7,6 +7,10 @@ description: |
|
||||
/freeze (blocks edits outside a specified directory). Use for maximum safety
|
||||
when touching prod or debugging live systems. Use when asked to "guard mode",
|
||||
"full safety", "lock it down", or "maximum safety". (gstack)
|
||||
triggers:
|
||||
- full safety mode
|
||||
- guard against mistakes
|
||||
- maximum safety
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -8,6 +8,10 @@ description: |
|
||||
0-10 score, and tracks trends over time. Use when: "health check",
|
||||
"code quality", "how healthy is the codebase", "run all checks",
|
||||
"quality score". (gstack)
|
||||
triggers:
|
||||
- code health check
|
||||
- quality dashboard
|
||||
- how healthy is codebase
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -19,6 +19,12 @@ allowed-tools:
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- debug this
|
||||
- fix this bug
|
||||
- why is this broken
|
||||
- root cause analysis
|
||||
- investigate this error
|
||||
hooks:
|
||||
PreToolUse:
|
||||
- matcher: "Edit"
|
||||
|
||||
@@ -14,6 +14,10 @@ allowed-tools:
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
sensitive: true
|
||||
triggers:
|
||||
- merge and deploy
|
||||
- land the pr
|
||||
- ship to production
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -8,6 +8,10 @@ description: |
|
||||
"show learnings", "prune stale learnings", or "export learnings".
|
||||
Proactively suggest when the user asks about past patterns or wonders
|
||||
"didn't we fix this before?"
|
||||
triggers:
|
||||
- show learnings
|
||||
- what have we learned
|
||||
- manage project learnings
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -23,6 +23,11 @@ allowed-tools:
|
||||
- Edit
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- brainstorm this
|
||||
- is this worth building
|
||||
- help me think through
|
||||
- office hours
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -9,6 +9,10 @@ description: |
|
||||
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
|
||||
voice-triggers:
|
||||
- "show me the browser"
|
||||
triggers:
|
||||
- open gstack browser
|
||||
- launch chromium
|
||||
- show me the browser
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -13,6 +13,10 @@ voice-triggers:
|
||||
- "connect agent"
|
||||
- "share my browser"
|
||||
- "remote browser access"
|
||||
triggers:
|
||||
- pair with agent
|
||||
- connect remote agent
|
||||
- share my browser
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -19,6 +19,11 @@ allowed-tools:
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- think bigger
|
||||
- expand scope
|
||||
- strategy review
|
||||
- rethink this plan
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -17,6 +17,10 @@ allowed-tools:
|
||||
- Glob
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- design plan review
|
||||
- review ux plan
|
||||
- check design decisions
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -27,6 +27,10 @@ allowed-tools:
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- developer experience review
|
||||
- dx plan review
|
||||
- check developer onboarding
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -22,10 +22,16 @@ allowed-tools:
|
||||
- AskUserQuestion
|
||||
- Bash
|
||||
- WebSearch
|
||||
triggers:
|
||||
- review architecture
|
||||
- eng plan review
|
||||
- check the implementation plan
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
# Plan Review Mode
|
||||
|
||||
Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
|
||||
@@ -295,6 +301,8 @@ Substitute values from the Completion Summary:
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Next Steps — Review Chaining
|
||||
|
||||
After displaying the Review Readiness Dashboard, check if additional reviews would be valuable. Read the dashboard output to see which reviews have already been run and whether they are stale.
|
||||
|
||||
@@ -17,6 +17,10 @@ allowed-tools:
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- qa report only
|
||||
- just report bugs
|
||||
- test but dont fix
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -24,12 +24,18 @@ allowed-tools:
|
||||
- Grep
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- qa test this
|
||||
- find bugs on site
|
||||
- test the site
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
{{BASE_BRANCH_DETECT}}
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
# /qa: Test → Fix → Verify
|
||||
|
||||
You are a QA engineer AND a bug-fix engineer. Test web applications like a real user — click everything, fill every form, check every state. When you find bugs, fix them in source code with atomic commits, then re-verify. Produce a structured report with before/after evidence.
|
||||
@@ -323,6 +329,8 @@ If the repo has a `TODOS.md`:
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Additional Rules (qa-specific)
|
||||
|
||||
11. **Clean working tree required.** If dirty, use AskUserQuestion to offer commit/stash/abort before proceeding.
|
||||
|
||||
@@ -14,6 +14,10 @@ allowed-tools:
|
||||
- Write
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
triggers:
|
||||
- weekly retro
|
||||
- what did we ship
|
||||
- engineering retrospective
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -17,6 +17,11 @@ allowed-tools:
|
||||
- Agent
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
triggers:
|
||||
- review this pr
|
||||
- code review
|
||||
- check my diff
|
||||
- pre-landing review
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
@@ -7,6 +7,10 @@ description: |
|
||||
Opens an interactive picker UI where you select which cookie domains to import.
|
||||
Use before QA testing authenticated pages. Use when asked to "import cookies",
|
||||
"login to the site", or "authenticate the browser". (gstack)
|
||||
triggers:
|
||||
- import browser cookies
|
||||
- login to test site
|
||||
- setup authenticated session
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -9,6 +9,10 @@ description: |
|
||||
the configuration to CLAUDE.md so all future deploys are automatic.
|
||||
Use when: "setup deploy", "configure deployment", "set up land-and-deploy",
|
||||
"how do I deploy with gstack", "add deploy config".
|
||||
triggers:
|
||||
- configure deploy
|
||||
- setup deployment
|
||||
- set deploy platform
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
@@ -19,12 +19,19 @@ allowed-tools:
|
||||
- AskUserQuestion
|
||||
- WebSearch
|
||||
sensitive: true
|
||||
triggers:
|
||||
- ship it
|
||||
- create a pr
|
||||
- push to main
|
||||
- deploy this
|
||||
---
|
||||
|
||||
{{PREAMBLE}}
|
||||
|
||||
{{BASE_BRANCH_DETECT}}
|
||||
|
||||
{{GBRAIN_CONTEXT_LOAD}}
|
||||
|
||||
# Ship: Fully Automated Ship Workflow
|
||||
|
||||
You are running the `/ship` workflow. This is a **non-interactive, fully automated** workflow. Do NOT ask for confirmation at any step. The user said `/ship` which means DO IT. Run straight through and output the PR URL at the end.
|
||||
@@ -345,6 +352,8 @@ For each classified comment:
|
||||
|
||||
{{LEARNINGS_LOG}}
|
||||
|
||||
{{GBRAIN_SAVE_RESULTS}}
|
||||
|
||||
## Step 4: Version bump (auto-decide)
|
||||
|
||||
**Idempotency check:** Before bumping, compare VERSION against the base branch.
|
||||
|
||||
@@ -6,6 +6,10 @@ description: |
|
||||
again. Use when you want to widen edit scope without ending the session.
|
||||
Use when asked to "unfreeze", "unlock edits", "remove freeze", or
|
||||
"allow all edits". (gstack)
|
||||
triggers:
|
||||
- unfreeze edits
|
||||
- unlock all directories
|
||||
- remove edit restrictions
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
|
||||
Reference in New Issue
Block a user