devops

Operate GitHub Actions pipelines, Terraform Cloud state, branching, and SemVer releases for a repository.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill devops-tedeuxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops
Source: https://github.com/tedeuxx/tadeumendonca-skills/tree/main/skills/devops
Command: npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill devops-tedeuxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It keeps every infrastructure mutation on exactly one route — the CI pipeline — by holding GitHub Actions workflows, Terraform Cloud state, branching models, secrets standards, and the permission floor in one place, so no one runs terraform apply from a laptop or pushes directly to a protected branch. ## Core Features & Use Cases - Branching model selection: Picks between trunk-single-env and gitflow-multi-env and derives protection rules, environments, and deploy triggers from that choice. - Pipeline wiring: Configures OIDC-based AWS roles, the secrets naming standard, build/test and infra-plan workflows, the Claude Code GitHub App, and SonarCloud quality gates. - Versioning and releases: Automates numeric SemVer via bump-my-version with a loop guard, conventional-commit release notes, and per-repo trigger models. - Use Case: When wiring a new repo's pipeline, cutting a release, bumping SemVer, or debugging a red Sonar gate, invoke this Skill to get the exact workflow YAML, secret names, and permission rules to apply. ## Quick Start Ask the agent to wire the CI pipeline and branch protection for this repository using the devops conventions.

Frequently Asked Questions about devops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up GitHub Actions with AWS OIDC instead of access keys?

Use aws-actions/configure-aws-credentials with permissions id-token: write so the pipeline assumes a dedicated AWS role via GitHub OIDC, with no AWS_ACCESS_KEY_ID secrets. The role's trust policy pins the repo's immutable OIDC subject, and its permissions policy is least-privilege.

How do I automate SemVer releases with bump-my-version in CI?

Configure .bumpversion.toml with a numeric-only parse and serialize pattern, commit and tag enabled, and a bump message starting with 'bump:'. A version workflow bumps the patch on every push to main, and both workflows skip commits starting with 'bump:' to prevent infinite CI loops.

Why is my required status check stuck on BLOCKED for docs-only PRs?

A required check gated by a trigger-level on.pull_request.paths filter never starts when the PR touches none of those paths, leaving branch protection permanently blocked. Drop paths from the pull_request trigger and gate heavy steps inside the job with dorny/paths-filter instead.

Should I use trunk-based development or GitFlow for my repo?

Count environments: one environment or a consumed artifact means trunk-single-env with main as the only long-lived branch, while multiple environments mean gitflow-multi-env with develop and main. The repo's CLAUDE.md should state the model explicitly.

Can I run terraform apply locally for a quick fix?

No. Every state mutation goes through the pipeline: plan on the PR, apply on merge. Local usage is read-only at most (fmt, validate, plan), and destroying live infrastructure happens by removing the resource from config and merging.

How do I wire SonarCloud into a GitHub Actions workflow?

Add the SonarSource/sonarqube-scan-action step after tests with SONAR_TOKEN and SONAR_HOST_URL set, and pass -Dsonar.qualitygate.wait=true so one step scans and fails the job on a red gate. Checkout needs fetch-depth: 0, and SonarCloud Automatic Analysis must be off.