
Gstack Game
Fold domain knowledge from GitHub Issues into gstack-game skill reference files via contribute-review, with contradiction checks and a PR.
Install
npx skills add https://github.com/fagemx/gstack-game --skill gstack-gameWhat is this skill?
- User-invocable contribute-review flow: /contribute-review #123 or scan mode for open issues
- Preamble bootstraps gstack-game bin/, session telemetry, and ~/.gstack/projects/{slug} artifact storage
- Reads GitHub Issues (gotchas, benchmarks, scoring calibration) and formats them for skill references/
- Contradiction check against existing reference material before opening a PR
- Cross-skill session tracking with gstack-config and proactive defaults
Adoption & trust: 1 installs on skills.sh; 36 GitHub stars; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Journey fit
Canonical shelf is Build/docs because the skill maintains living reference docs inside a game skill pack, though it runs whenever issue-driven knowledge lands. Docs subphase fits converting Issue narratives into references/ artifacts the agent reads during game review and config sessions.
Common Questions / FAQ
Is Gstack Game safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Gstack Game
<!-- Internal maintenance skill — edit this file directly --> ## Preamble (run first) ```bash _GD_VERSION="0.3.0" # Find gstack-game bin directory (installed in project or standalone) _GG_BIN="" for _p in ".claude/skills/gstack-game/bin" ".claude/skills/game-review/../../gstack-game/bin" "$(dirname "$(readlink -f .claude/skills/game-review/SKILL.md 2>/dev/null)" 2>/dev/null)/../../bin"; do [ -f "$_p/gstack-config" ] && _GG_BIN="$_p" && break done [ -z "$_GG_BIN" ] && echo "WARN: gstack-game bin/ not found, some features disabled" # Project identification _SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)") _BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown") _USER=$(whoami 2>/dev/null || echo "unknown") # Session tracking mkdir -p ~/.gstack/sessions touch ~/.gstack/sessions/"$PPID" _PROACTIVE=$([ -n "$_GG_BIN" ] && "$_GG_BIN/gstack-config" get proactive 2>/dev/null || echo "true") _TEL_START=$(date +%s) _SESSION_ID="$-$(date +%s)" # Shared artifact storage (cross-skill, cross-session) mkdir -p ~/.gstack/projects/$_SLUG _PROJECTS_DIR=~/.gstack/projects/$_SLUG # Telemetry mkdir -p ~/.gstack/analytics echo '{"skill":"contribute-review","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'"$_SLUG"'","branch":"'"$_BRANCH"'"}' >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true echo "SLUG: $_SLUG" echo "BRANCH: $_BRANCH" echo "PROACTIVE: $_PROACTIVE" echo "PROJECTS_DIR: $_PROJECTS_DIR" echo "GD_VERSION: $_GD_VERSION" ``` **Shared artifact directory:** `$_PROJECTS_DIR` (`~/.gstack/projects/{slug}/`) stores all skill outputs: - Design docs from `/game-ideation` - Review reports from `/game-review`, `/balance-review`, etc. - Player journey maps from `/player-experience` All skills read from this directory on startup to find prior work. All skills write their output here for downstream consumption. If `PROACTIVE` is `"false"`, do not proactively suggest gstack-game skills. ## AskUserQuestion Format (Game Design) **ALWAYS follow this structure for every AskUserQuestion call:** 1. **Re-ground:** Project, branch, what game/feature is being reviewed. (1-2 sentences) 2. **Simplify:** Plain language a smart 16-year-old gamer could follow. Use game examples they'd know (Minecraft, Genshin, Among Us, etc.) as analogies. 3. **Recommend:** `RECOMMENDATION: Choose [X] because [one-line reason]` — include `Player Impact: X/10` for each option. Calibration: 10 = fundamentally changes player experience, 7 = noticeable improvement, 3 = cosmetic/marginal. 4. **Options:** Lettered: `A) ... B) ... C) ...` with effort estimates (human: ~X / CC: ~Y). **Game-specific vocabulary — USE these terms, don't reinvent:** - Core loop, session loop, meta loop - FTUE (First Time User Experience), aha moment, churn point - Retention hook (D1, D7, D30) - Economy: sink, faucet, currency, exchange rate - Progression: skill gate, content gate, time gate - Bartle types: Achiever, Explorer, Socializer, Killer - Difficulty curve, flow state, friction point - Whale, dolphin, minnow (spending tiers) ## Completion Status Protocol DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT. Escalation after 3 failed attempts. ## Telemetry (run last) ```bash _TEL_END=$(date +%s) _TEL_DUR=$(( _TEL_END - _TEL_START )) [ -n "$_GG_BIN" ] && "$_GG_BIN/gstack-telemetry-log" \ --skill "contribute-review" --duration "$_TEL_DUR" --outcome "OUTCOME" \ --used-browse "false" --session-id "$_SESSION_ID" 2>/dev/null & ``` ## Load References (BEFORE any interaction) ```bash SKILL_DIR="$(find . -path '*skills/contribute-review/references' -type d 2>/dev/null | head -1)" [