team-release — community team-release, Claude-Code-Game-Studios, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Project Management Agents requiring structured game development pipelines and release team orchestration. Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.

Donchitos Donchitos
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
41
Canonical Locale
en
Detected Body Locale
en

Ideal for Project Management Agents requiring structured game development pipelines and release team orchestration. Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.

Core Value

Empowers agents to streamline game development through automated pipelines, utilizing subagents like release-manager for versioning and deployment, and qa-lead for testing, all while ensuring user approval at each phase transition via AskUserQuestion protocol.

Ideal Agent Persona

Ideal for Project Management Agents requiring structured game development pipelines and release team orchestration.

↓ Capabilities Granted for team-release

Orchestrating release teams through structured pipelines
Automating game development workflows with subagents
Streamlining deployment and changelog management

! Prerequisites & Limits

  • Requires user approval at each phase transition
  • Specifically designed for game development studios

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is team-release?

Ideal for Project Management Agents requiring structured game development pipelines and release team orchestration. Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.

How do I install team-release?

Run the command: npx killer-skills add Donchitos/Claude-Code-Game-Studios. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for team-release?

Key use cases include: Orchestrating release teams through structured pipelines, Automating game development workflows with subagents, Streamlining deployment and changelog management.

Which IDEs are compatible with team-release?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for team-release?

Requires user approval at each phase transition. Specifically designed for game development studios.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Donchitos/Claude-Code-Game-Studios. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use team-release immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

team-release

Install team-release, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

When this skill is invoked, orchestrate the release team through a structured pipeline.

Decision Points: At each phase transition, use AskUserQuestion to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase.

Team Composition

  • release-manager — Release branch, versioning, changelog, deployment
  • qa-lead — Test sign-off, regression suite, release quality gate
  • devops-engineer — Build pipeline, artifacts, deployment automation
  • producer — Go/no-go decision, stakeholder communication, scheduling

How to Delegate

Use the Task tool to spawn each team member as a subagent:

  • subagent_type: release-manager — Release branch, versioning, changelog, deployment
  • subagent_type: qa-lead — Test sign-off, regression suite, release quality gate
  • subagent_type: devops-engineer — Build pipeline, artifacts, deployment automation
  • subagent_type: producer — Go/no-go decision, stakeholder communication

Always provide full context in each agent's prompt (version number, milestone status, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 3 agents can run simultaneously).

Pipeline

Phase 1: Release Planning

Delegate to producer:

  • Confirm all milestone acceptance criteria are met
  • Identify any scope items deferred from this release
  • Set the target release date and communicate to team
  • Output: release authorization with scope confirmation

Phase 2: Release Candidate

Delegate to release-manager:

  • Cut release branch from the agreed commit
  • Bump version numbers in all relevant files
  • Generate the release checklist using /release-checklist
  • Freeze the branch — no feature changes, bug fixes only
  • Output: release branch name and checklist

Phase 3: Quality Gate (parallel)

Delegate in parallel:

  • qa-lead: Execute full regression test suite. Test all critical paths. Verify no S1/S2 bugs. Sign off on quality.
  • devops-engineer: Build release artifacts for all target platforms. Verify builds are clean and reproducible. Run automated tests in CI.

Phase 4: Localization and Performance

Delegate (can run in parallel with Phase 3 if resources available):

  • Verify all strings are translated (delegate to localization-lead if available)
  • Run performance benchmarks against targets (delegate to performance-analyst if available)
  • Output: localization and performance sign-off

Phase 5: Go/No-Go

Delegate to producer:

  • Collect sign-off from: qa-lead, release-manager, devops-engineer, technical-director
  • Evaluate any open issues — are they blocking or can they ship?
  • Make the go/no-go call
  • Output: release decision with rationale

Phase 6: Deployment (if GO)

Delegate to release-manager + devops-engineer:

  • Tag the release in version control
  • Generate changelog using /changelog
  • Deploy to staging for final smoke test
  • Deploy to production
  • Monitor for 48 hours post-release

Phase 7: Post-Release

  • release-manager: Generate release report (what shipped, what was deferred, metrics)
  • producer: Update milestone tracking, communicate to stakeholders
  • qa-lead: Monitor incoming bug reports for regressions
  • Schedule post-release retrospective if issues occurred

Output

A summary report covering: release version, scope, quality gate results, go/no-go decision, deployment status, and monitoring plan.

Related Skills

Looking for an alternative to team-release or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer