القائمة
End-to-end issue pipeline: plan → implement → review → merge. Dispatches parallel sub-agents with worktree isolation. Usage: /issue-pipeline 33 34 35 [--skip-plan] [--skip-review] [--no-merge]
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Game development workflow skills for Claude Code. 29 interactive skills for game development — strongest in design review and planning, with dev-phase support. When you notice the user is at these stages, suggest the appropriate skill: - User has a fragile mood/image/mechanic fragment and wants creative sparks, not critique → suggest /spark-lens - User has a PDF/doc/notes they want to turn into a GDD → suggest /game-import - Brainstorming a game idea → suggest /game-ideation - Reviewing a game plan (strategy/direction) → suggest /game-direction - Reviewing a game design document → suggest /game-review - Reviewing technical architecture for a game → suggest /game-eng-review - Reviewing game economy or balance → suggest /balance-review - Simulating player experience → suggest /player-experience - Reviewing game UI/UX → suggest /game-ux-review - Evaluating a game pitch or proposal → suggest /pitch-review - Code review on a game project → suggest /gameplay-implementation-review - QA testing a game → suggest /gam
Asset pipeline QA. Checks naming conventions, file formats, performance budgets, style consistency (deviation counting, not quality judgment), and pipeline health. Use when you have game assets to audit — NOT for in-engine visual review (use /game-visual-qa) or architecture review (use /game-eng-review).
Use when a game has numbers that need checking — difficulty curves, currency flow, gacha rates, progression pacing, grind ratios, or pay-to-win concerns. Not for visual design, narrative, core loop evaluation (use /game-review), or player experience walkthrough (use /player-experience).
Use when a prototype or build exists and you need to know: is this worth playing? Not QA (use /game-qa for bugs), not feel (use /feel-pass for responsiveness), not code (use /gameplay-implementation-review). This evaluates the EXPERIENCE: does the loop close, does the session hold, does the player want to come back.
Safety mode. Warns before destructive commands (rm -rf, DROP TABLE, git push -f, force delete). Does NOT restrict file editing scope — use /guard for that.
Use when a prototype or playable build exists and you need to know if a mechanic feels alive or dead — responsiveness, impact, rhythm, feedback chains, dead time. Not for GDD review (use /game-review), not for code review (use /gameplay-implementation-review), not for bug hunting (use /game-debug). Requires a playable build or detailed video of gameplay.
| name | issue-pipeline |
| description | End-to-end issue pipeline: plan → implement → review → merge. Dispatches parallel sub-agents with worktree isolation. Usage: /issue-pipeline 33 34 35 [--skip-plan] [--skip-review] [--no-merge] |
| user_invocable | true |
You orchestrate the full lifecycle of GitHub issues through parallel sub-agents. Each phase runs all issues concurrently in isolated worktrees.
Parse $ARGUMENTS to get issue numbers and flags.
Examples:
/issue-pipeline 33 34 35 — full pipeline (plan → implement → review → merge)/issue-pipeline 33 34 --skip-plan — issues already have plans, skip to implement/issue-pipeline 33 34 --skip-review --no-merge — implement only, no review or merge/issue-pipeline 33 — single issue, full pipelineIf no issue numbers provided, ask: "Which issues? Provide issue numbers separated by spaces."
Flags:
--skip-plan — Skip plan phase (issues already have planned label + plan comments)--skip-review — Skip review phase, merge after implement--no-merge — Stop after review, don't auto-merge--dry-run — Show what would happen without executingBefore starting, verify all issues exist and check their state:
for num in {issue_numbers}; do
gh issue view $num --json number,title,labels,state --jq '"\(.number) [\(.labels | map(.name) | join(","))] \(.state) — \(.title)"'
done
Report findings:
planned label → can skip plan phaseplanned label → need plan phaseSkip if: --skip-plan flag OR issue already has planned label.
For each issue needing a plan, launch a sub-agent:
Agent tool parameters:
description: "Plan issue #{number}"
isolation: "worktree"
run_in_background: true
prompt: |
You are working on GitHub issue #{number} for gstack-game at {repo_root}.
Execute the /issue-plan workflow:
1. Read the skill at {repo_root}/.claude/skills/issue-plan/SKILL.md
2. Follow its instructions for issue #{number}
This means: Research → Innovate → Plan, posting all 3 phases to the issue.
IMPORTANT:
- You are in a worktree — do NOT modify source code, planning only
- Post all findings to the GitHub issue as comments
- Add the "planned" label when done
Wait for ALL plan agents to complete. Report status table.
For each issue with a plan, launch a sub-agent:
Agent tool parameters:
description: "Implement issue #{number}"
isolation: "worktree"
run_in_background: true
prompt: |
You are implementing GitHub issue #{number} for gstack-game at {repo_root}.
Execute the /issue-action workflow:
1. Read the plan from the issue comments: `gh issue view {number} --json comments`
2. Also check for local artifacts: `.tmp/deep-dive/issue-{number}/plan.md`
3. Read the skill at {repo_root}/.claude/skills/issue-action/SKILL.md
4. Follow its instructions for issue #{number}
IMPORTANT:
- You are in a worktree — create a feature branch, make changes, commit
- Edit .tmpl files, never generated .md directly
- Run `bun run build` after template changes
- Run `bun test` — all tests must pass before creating PR
- Create a PR with `gh pr create` — include "Closes #{number}" in the body
- Do NOT merge the PR
Wait for ALL implement agents to complete. Collect PR URLs/numbers. Report status table.
Skip if: --skip-review flag.
For each PR created in Phase 2, launch a sub-agent:
Agent tool parameters:
description: "Review PR #{pr_number}"
isolation: "worktree"
run_in_background: true
prompt: |
You are reviewing PR #{pr_number} for gstack-game at {repo_root}.
Execute the /pr-review-loop workflow:
1. Read the skill at {repo_root}/.claude/skills/pr-review-loop/SKILL.md
2. Follow its instructions for PR #{pr_number}
IMPORTANT:
- You are in a worktree
- If fixes are needed, check out the PR branch, fix, commit, and push
- The review loop continues until LGTM or max 3 iterations
Wait for ALL review agents to complete. Report verdicts.
Skip if: --no-merge flag.
For each PR with LGTM verdict:
gh pr merge {pr_number} --merge --delete-branch
For PRs without LGTM: report them as needing manual review.
After all merges, sync main:
git checkout main && git pull
Report final status table.
isolation: "worktree" — never work on main directlyrun_in_background: true — maximize parallelismgit checkout main && git pull to pick up merged changes.tmpl files, run bun run build to regenerate .md, run bun test (14 tests)skills/shared/preamble-*.md, ALL 28 SKILL.md files are regeneratedfeat: / fix: / test: / docs:)--merge (not squash) to preserve commit historyAfter each phase:
| Issue | Phase | Status | Details |
|-------|-----------|--------|---------|
| #33 | plan | ✅ | Plan posted to issue |
| #34 | plan | ⏭️ | Already planned |
| #35 | implement | ✅ | PR #38 created |
| #36 | implement | ❌ | bun test failed |
After merge:
| Issue | PR | Plan | Implement | Review | Merge | Result |
|-------|-----|------|-----------|--------|-------|--------|
| #33 | #38 | ✅ | ✅ | ✅ | ✅ | DONE |
| #34 | #39 | ⏭️ | ✅ | ✅ | ✅ | DONE |
| #35 | #40 | ✅ | ✅ | ⚠️ | ❌ | NEEDS REVIEW |