Menu
Write commit messages following the Conventional Commits format. Use when composing, reviewing, or fixing git commit messages.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Amazon Web Services CLI operations and infrastructure patterns for AWS resource management. Activate when user mentions: aws, AWS, Amazon Web Services, EC2, EKS, ECS, S3, RDS, Lambda, CloudFormation, CloudWatch, IAM roles, IAM policies, aws cli commands, AWS deployment, AWS infrastructure, ECR, ALB, NLB, VPC, Route53, DynamoDB, SQS, SNS, EventBridge, Systems Manager, Secrets Manager, CloudTrail, AWS Organizations. Use for: AWS resource provisioning, aws cli commands, AWS service configuration, infrastructure-as-code for AWS, AWS best practices, OIDC authentication, IAM roles for service accounts (IRSA), AWS security patterns, multi-region deployments, high availability configurations, cost optimization, disaster recovery, Spot instances. Do NOT use for: GCP-specific resources, Azure-specific resources, Kubernetes manifests (use kubernetes-native skill), generic shell scripting unrelated to AWS, Terraform/Pulumi DSL syntax (use terraform-modules or pulumi-cdk skills for IaC DSLs).
AWS EKS cluster provisioning, configuration best practices, security hardening, cost optimization, IRSA (IAM Roles for Service Accounts), VPC CNI networking, node group management, cluster addons, and Kubernetes 1.31+ features including Gateway API v1 and native sidecar containers. Activate when user mentions: AWS EKS, Elastic Kubernetes Service, EKS cluster, eksctl, EKS node groups, managed node groups, self-managed nodes, Fargate profiles, EKS addons, VPC CNI, CoreDNS, kube-proxy, EKS OIDC provider, IRSA, IAM roles for service accounts, EKS security groups, pod security groups, EKS encryption, KMS encryption, EKS logging, control plane logs, EKS access entries, EKS cluster autoscaler, Karpenter, Gateway API on EKS, AWS Load Balancer Controller, EBS CSI driver, EFS CSI driver. Use for: EKS cluster architecture design, Terraform/Pulumi EKS provisioning, security configuration, IRSA setup, VPC networking for EKS, node group optimization, spot instance integration, cluster addon management, multi-AZ high availa
Dockerfile best practices, multi-stage builds, security scanning patterns, CI/CD validation pipelines, and container optimization strategies. Activate when user mentions: Dockerfile, container image, multi-stage build, container security, image optimization, docker build, container layers, base image, distroless, alpine, scratch image, container scanning, vulnerability scanning, dockerfile lint, hadolint, trivy, security pipeline, SBOM generation, container validation, CI/CD security gates, image attestation. Use for: Dockerfile generation patterns, security hardening, build optimization, layer caching strategies, CI/CD security integration, vulnerability management, SBOM generation, policy-as-code validation. Do NOT use for: Runtime orchestration (use kubernetes-native skill), CI/CD pipelines (use github-actions-iac skill), infrastructure provisioning (use terraform-patterns skill).
Crossplane composition patterns for cloud-native infrastructure provisioning. Provides XRD (CompositeResourceDefinition), Composition, and Claim patterns for AWS, Azure, GCP resources with security best practices, validation pipelines, and hallucination detection for AI-generated compositions. Activate when user mentions: crossplane, XRD, composite resource, composition, claim, provider config, managed resources, crossplane composition, infrastructure composition, declarative infrastructure, control plane. Use for: Generating Crossplane compositions, XRDs, Claims, ProviderConfigs, and managed resource patterns following cloud-native best practices with multi-phase validation and cost optimization. Do NOT use for: Direct Terraform/Pulumi code, CloudFormation templates, Kubernetes operators (unless Crossplane-specific), raw cloud provider APIs.
GitHub Actions CI/CD pipeline patterns for IaC deployments. Provides secure workflow configurations with OIDC authentication, multi-environment deployment strategies, reusable workflow architectures, and infrastructure validation with modern security scanning tools. Activate when user mentions: GitHub Actions, CI/CD, workflow, pipeline, deployment, OIDC, GitHub workflow, actions workflow, CI pipeline, continuous deployment, automated deployment, workflow file, .github/workflows, reusable workflows Use for: Generating GitHub Actions workflows for Terraform, Kubernetes, Helm deployments with security best practices (OIDC, Trivy scanning, validation gates, reusable patterns). Do NOT use for: GitLab CI, Jenkins, CircleCI, or other CI/CD platforms. For those, recommend platform-specific tooling.
GitLab CI/CD pipeline patterns for Infrastructure-as-Code deployments. Provides secure .gitlab-ci.yml configurations with OIDC authentication, DAG pipeline optimization, GitLab Agent for Kubernetes GitOps integration, reusable job templates, multi-environment deployment strategies, and security scanning with modern validation tools. Activate when user mentions: GitLab CI, .gitlab-ci.yml, GitLab pipelines, DAG pipelines, GitLab Agent, GitLab Runner, GitLab GitOps, CI/CD pipelines, stages, jobs, rules, needs, artifacts, GitLab deployment, GitLab security scanning, parent-child pipelines, pipeline efficiency, Flux integration with GitLab Agent. Use for: Generating GitLab CI/CD pipelines for Terraform, Kubernetes, Helm, Docker builds with security best practices (OIDC, workload identity, DAG optimization, security scanning, validation gates, artifact management, and GitLab Agent for GitOps). Do NOT use for: GitHub Actions, Jenkins, CircleCI, or other CI/CD platforms. For those, recommend platform-specific tooling
| name | conventional-commits |
| description | Write commit messages following the Conventional Commits format. Use when composing, reviewing, or fixing git commit messages. |
Write commit messages in the Conventional Commits format.
<type>: <description>
feat - a new featurefix - a bug fixdocs - documentation changeschore - other changesfeat: add user login
fix: fixed the bug in the parser that was crashing sometimes