workflow▌

Triage GitHub issues through a label-based state machine for efficient issue management.

Turn a single Claude Code session into a full game development studio with 49 agents and 72 skills.

Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices.

You are a workflow automation architect who has seen both the promise and the pain of these platforms. You've migrated teams from brittle cron jobs to durable execution and watched their on-call burden drop by 80%.

Guidelines for commits, pull requests, CI workflows, and secure dependency management. \n \n Emphasizes atomic, focused commits with clear messages; recommends git rebase -i for clean history and avoiding mixed logic/formatting changes \n PR best practices include keeping changes small and focused, running tests before submission, and using WIP states in GitHub Actions when needed \n Security checklist: never commit .env files, credentials, or secrets \n Dependency additions require a license fi

Structural design patterns and principles for reliable multi-step Claude Code workflow skills. \n \n Covers five workflow patterns (routing, sequential pipeline, linear progression, safety gate, task-driven) with numbered phases, entry/exit criteria, and decision trees for pattern selection \n Enforces progressive disclosure: SKILL.md stays under 500 lines with details split into references/ and workflows/ directories, one level deep \n Provides 20 anti-patterns with before/after fixes, covering

Design durable distributed workflows with Temporal, separating orchestration logic from external interactions. \n \n Workflows handle orchestration and decision-making (must be deterministic); activities handle external calls like APIs and databases (must be idempotent) \n Implements saga pattern with compensation for distributed transactions, entity workflows for long-lived state management, and fan-out/fan-in for parallel execution \n Automatic state preservation across failures via event hist

Post a Google Drive file announcement to a Google Chat space. \n \n Requires a Drive file ID and Chat space name; optionally accepts a custom announcement message \n Automatically fetches the file name from Drive to construct the announcement \n Supports multiple output formats: JSON (default), table, YAML, and CSV \n Pairs with gws drive +upload for a complete upload-and-announce workflow \n

Aggregates today's calendar meetings and open tasks into a single standup summary. \n \n Combines Google Calendar agenda with task list data for a unified daily briefing \n Supports multiple output formats: JSON (default), table, YAML, and CSV \n Read-only operation that never modifies calendar or task data \n Requires gws binary and authentication setup from the shared skill module \n

Weekly summary combining this week's calendar meetings and unread email count. \n \n Aggregates two data sources: upcoming meetings from Google Calendar and unread message count from Gmail \n Read-only operation that never modifies any data \n Supports multiple output formats: JSON (default), table, YAML, and CSV for flexible integration with other tools \n Requires prior authentication setup via the shared gws-shared skill module \n