terraform-modules

Triage a GitHub issue in the zachreborn/terraform-modules Terraform/OpenTofu module library: classify it as a bug or feature, validate it against the repository's minimum reporting standards, and move it through the issue-to-implementation pipeline by posting a single comment and applying the correct label (needs-info or ready-for-spec) via the gh CLI. Use this skill whenever you are asked to triage, validate, classify, or label an incoming issue for this repo, or when an issue is opened or edited and needs its pipeline state set. This skill is the canonical source for the triage agent; the Issue Triage GitHub Actions workflow invokes it with per-run context.

Generate a technical specification for a triaged GitHub issue in the zachreborn/terraform-modules Terraform/OpenTofu module library, following the repository's spec template and conventions, then open a spec PR and advance the issue to spec-ready-for-review. Use this skill whenever you are asked to write, author, or generate a spec for an issue in this repo, or when an issue reaches the ready-for-spec stage of the pipeline. This skill is the canonical source for the spec-generation agent; the Spec Generation GitHub Actions workflow invokes it with per-run context.

Implement an approved spec in the zachreborn/terraform-modules Terraform/OpenTofu module library, treating the committed spec file as the source of truth, then open an implementation PR that fills the repo PR template and links the originating issue. Use this skill whenever you are asked to implement, build, or code an approved spec for this repo, or when an issue reaches the spec-approved stage of the pipeline. This skill is the canonical source for the implementation agent; the Implementation GitHub Actions workflow invokes it with per-run context.

Guide for writing git commit messages and selecting a commit standard. Use this skill whenever the user asks how to format a commit message, what commit type to use, how to write a good commit, which commit convention to follow, how to set up commitlint or semantic-release, what Conventional Commits are, how commit messages relate to versioning, or asks about Angular/Gitmoji/Linux commit formats. Also trigger when the user is about to run `git commit` and seems uncertain about the message, when they ask "what type should this be?", or when they mention conventional commits, semantic versioning, or changelog generation.