sumik

前回のgitタグから現在までの変更履歴を分析し、Keep a Changelog形式でCHANGELOG.mdエントリーとプロジェクトファイルのバージョンを自動生成・更新する

会話履歴とステージ済み変更からConventional Commits準拠のコミットメッセージを生成・表示

E2E Chrome DevTools MCP を使って E2E テストを実行する。docs/e2e-testing/RUNBOOK.md のランブックを読み込んで実行。

Webアプリのコードを分析してユーザーストーリー（docs/user-story.md）とE2Eテストケース（docs/e2e.md）を作成・更新する。コードベース全体を走査して、ペルソナ・受入基準・Mermaid図付きのドキュメントを生成。

CHANGELOG.mdから指定バージョンのエントリーを抽出し、その内容をメッセージとするannotated tagを自動作成する

Token-efficient app development agent using /serena command for structured problem-solving. Specializes in full-stack implementation (components, APIs, systems, tests) with maximum token efficiency. Use proactively when /serena command is explicitly requested or when token-efficient structured development is needed for complex multi-step implementations.

AWS cloud specialized Tachikoma execution agent. Handles Lambda, API Gateway, DynamoDB, CDK, EKS, S3, Bedrock, and all AWS services including security (IAM, KMS, GuardDuty), cost optimization, and SRE operations. Use proactively when working with AWS services, CDK infrastructure, serverless applications, or AWS-related code. Detects: cdk.json, samconfig.toml, serverless.yml, @aws-sdk in package.json, or boto3 in Python deps.

Google Cloud specialized Tachikoma execution agent. Handles Cloud Run (serverless deployment), BigQuery (SQL analytics, advanced operations, ML), GCP security (IAM, VPC, KMS, Zero Trust, DevSecOps), data engineering (pipelines, governance, lakehouse/BigLake/Dataplex, ingestion, real-time analytics), networking (VPC, LB, CDN, hybrid), Memorystore (Redis/Memcached), enterprise architecture (account design, migration), compute selection (GCE/GKE/GAE/Run/Functions), GKE orchestration, monitoring design, BI visualization (Looker), workflow orchestration (Composer/Dataform), and ML analytics (Vertex AI, BigQuery ML). Use proactively when working with Google Cloud services, GCP infrastructure, or cloud-native applications on GCP. Detects: cloudbuild.yaml, .gcloudignore, @google-cloud packages, Looker, Dataplex.

Infrastructure/DevOps specialized Tachikoma execution agent. Handles Docker/Podman containers, Compose orchestration, CI/CD pipeline configuration, and DevOps methodology. Use proactively when working with Dockerfiles, Containerfiles, docker-compose.yml, CI/CD configs, or implementing DevOps practices. Detects: Dockerfile, Containerfile, docker-compose.*, or podman-related files.

Terraform IaC specialized Tachikoma execution agent. Handles HCL configuration, module design, state management, Terragrunt wrapper patterns, infrastructure testing, and cloud provider resources. Use proactively when working with .tf files, terragrunt.hcl, or infrastructure as code definitions. Detects: .tf files or terragrunt.hcl.

Behavioral design methodology for products that change user behavior using CREATE Action Funnel (Cue, Reaction, Evaluation, Ability, Timing) and three strategies (cheat, habit, conscious action). Use when designing product features that aim to change user habits, increase engagement, or guide users toward beneficial actions. For visual UI/UX design principles, use designing-ux instead. For training program design and facilitation methodology, use designing-training instead. For human-centered design thinking process (user research, ideation, prototyping), use designing-ux instead.

Clean Architecture and Domain-Driven Design (DDD) unified guide covering the Dependency Rule, concentric layer model (Entities, Use Cases, Interface Adapters, Frameworks & Drivers), component principles (REP/CCP/CRP, ADP/SDP/SAP), Screaming Architecture, Humble Objects, and DDD strategic/tactical patterns (Bounded Context, Ubiquitous Language, Context Mapping, Value Object, Entity, Aggregate, Event Sourcing, CQRS, Saga, data decomposition). Use when designing application layer structure, enforcing dependency rules, separating business logic from frameworks/UI/databases, modeling complex domains with DDD patterns, or mapping Bounded Contexts to Clean Architecture layers. For code-level clean practices, use writing-clean-code. For distributed/infrastructure patterns, use architecting-infrastructure. For evolutionary architecture and microservices intro, see ARCHITECTURE-EVOLUTION.md. For project foundations and team practices, use practicing-software-engineering.

Semantic Versioning 2.0.0仕様に基づくバージョン判断ガイド。MAJOR/MINOR/PATCH判定、プレリリース・ビルドメタデータ、範囲指定を提供。 REQUIRED for all version-related decisions. Use when determining version bumps, creating releases, or managing dependencies. For commit message format (type/scope/BREAKING CHANGE), use writing-conventional-commits instead.

Data architecture patterns covering read-side optimization (replicas, materialized views, CQRS, CDC, event sourcing), domain-based decomposition, polyglot persistence, and caching strategies (cache-aside, read-through, write-through, write-around). Use when designing data flow architecture, choosing read scalability strategies, or implementing caching for enterprise systems. For microservices patterns (Saga, granularity), use architecting-infrastructure instead. For DDD domain modeling, use applying-clean-architecture instead. For database engine internals, use developing-databases instead. For relational DB schema design, use developing-databases instead. For GCP-specific data services (BigQuery, Dataflow, Dataproc), lakehouse (BigLake, Dataplex), and BigQuery advanced operations (editions, HA/DR), use developing-google-cloud instead.

Vendor-neutral infrastructure and system architecture patterns. Infrastructure: 127 patterns for availability (HA, DR, backup), security, performance/scalability, operations, network/storage configuration, and cloud. Modernization: socio-technical strategy, domain redesign, trade-off analysis (code/API/system/meta levels). Microservices: CQRS, Event Sourcing, Saga, distributed transactions, service granularity, data ownership, resilience, messaging. Use when designing infrastructure, evaluating non-functional requirements, modernizing legacy systems, making architectural trade-offs, or designing microservices.

1 hook across 1 event