Agent skill

Tsh Implementing CI CD

by TheSoftwareHouse in TheSoftwareHouse/copilot-collections

CI/CD pipeline design patterns and deployment strategies. An agent skill from TheSoftwareHouse/copilot-collections.

Install Tsh Implementing CI CD

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .claude/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .claude/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .agents/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .agents/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .cursor/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .cursor/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/TheSoftwareHouse/copilot-collections.git --path .github/skills/tsh-implementing-ci-cd

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .gemini/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .gemini/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .github/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .github/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install TheSoftwareHouse/copilot-collections tsh-implementing-ci-cd --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TheSoftwareHouse/copilot-collections.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/tsh-implementing-ci-cd .opencode/skills/tsh-implementing-ci-cd && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "tsh-implementing-ci-cd" agent skill from https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/tsh-implementing-ci-cd into .opencode/skills/tsh-implementing-ci-cd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tsh-implementing-ci-cd", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: tsh-implementing-ci-cd
GitHub stars: 284
Token cost: ~1.6k tokens
SKILL.md length: 538 words
Files: 1
Skills in repo: 21
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

CI/CD pipeline design patterns and deployment strategies. An agent skill from TheSoftwareHouse/copilot-collections.

Works in 6 steps: Discover context → Use… → Detect platform → Check for CI config… → Look up syntax → Use context7 for… → …
Designing pipelines
SKILL.md covers When to Use, Platform Detection, Pipeline Structure and Deployment Strategy Decision, plus 7 more sections
Calls terraform, nx and turbo

What it does

Tsh Implementing CI CD is an agent skill from TheSoftwareHouse/copilot-collections. CI/CD pipeline design patterns and deployment strategies. Use when designing pipelines, implementing deployment strategies, or setting up automated delivery.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD, Deployment and Design patterns. It works with GitHub Actions, Amazon Web Services, Bitbucket and GitLab. The repository describes itself as: Opinionated AI-enabled workflows for product engineering. The licence is MIT.

When your agent uses it

Designing pipelines
Implementing deployment strategies
Setting up automated delivery

Example prompts

“/tsh-implementing-ci-cd”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Discover context → Use tsh-technical-context-discovering to find existing CI patterns
Detect platform → Check for CI config files listed above
Look up syntax → Use context7 for platform-specific YAML syntax
Choose deployment strategy → Use decision table above
Configure credentials → Use tsh-managing-secrets skill
Validate → Run pipeline in dry-run/plan mode first

What it can do on your machine

Read from SKILL.md and the folder at commit 2fbe51e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- terraform
- nx
- turbo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tsh Implementing CI CD loads about 1.6k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 538 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~45
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheSoftwareHouse/copilot-collections at commit 2fbe51e, republished under its MIT licence (© TheSoftwareHouse). 538 words, ~1,568 tokens.

Download SKILL.mdSave it as .claude/skills/tsh-implementing-ci-cd/SKILL.md (or your agent's skills folder).

name: tsh-implementing-ci-cd
description: CI/CD pipeline design patterns and deployment strategies. Use when designing pipelines, implementing deployment strategies, or setting up automated delivery.
user-invocable: false

CI/CD Pipeline Patterns

When to Use

Designing new CI/CD pipelines
Implementing deployment strategies (rolling, blue-green, canary)
Setting up GitOps workflows
Configuring secure CI/CD credentials

Platform Detection

Check which CI/CD platform the project uses:

.github/workflows/*.yml → GitHub Actions
bitbucket-pipelines.yml → Bitbucket Pipelines
.gitlab-ci.yml → GitLab CI
azure-pipelines.yml → Azure Pipelines
Jenkinsfile → Jenkins

Use context7 to look up platform-specific syntax for the detected platform.

Pipeline Structure

Lint → Test → Build → Deploy (staging) → Deploy (production)
         ↓
    Artifacts & Caching

Rule: Each stage should be independent and cacheable.

Deployment Strategy Decision

Strategy	Use When	Rollback	Risk
Rolling	Stateless apps, can tolerate mixed versions	Slow	Low
Blue-Green	Need instant rollback, DB migrations	Instant	Low
Canary	High traffic, want gradual validation	Instant	Very Low
Recreate	Dev/test, breaking changes only	Slow	High

Credentials Strategy Decision

Scenario	Approach
AWS from GitHub/GitLab	OIDC federation (no long-lived keys)
AWS from Bitbucket	Repository variables + IAM role
Multi-cloud	HashiCorp Vault with CI/CD auth
Simple/small team	Platform native secrets

Rule: Prefer OIDC federation over long-lived access keys. Use tsh-managing-secrets skill for implementation details.

Monorepo Strategy

Tool	Detection	Approach
Nx	`nx.json`	`nx affected --target=build`
Turborepo	`turbo.json`	`turbo run build --filter=...[origin/main]`
None	-	Path filtering in CI config

Process

Discover context → Use tsh-technical-context-discovering to find existing CI patterns
Detect platform → Check for CI config files listed above
Look up syntax → Use context7 for platform-specific YAML syntax
Choose deployment strategy → Use decision table above
Configure credentials → Use tsh-managing-secrets skill
Validate → Run pipeline in dry-run/plan mode first

Checklist

Secrets stored in platform secret manager (not in code)
Caching configured for dependencies
Branch protection enabled on main/master
Environment approvals required for production
Rollback procedure documented
Pipeline uses pinned versions (not @latest)

Anti-Patterns

Storing secrets in code or logs
Skipping tests for "quick fixes"
Using latest tags in production images
Deploying without artifact verification
Direct pushes to main/master

Infrastructure as Code Pipelines

Terraform/Terragrunt Pipeline Structure

Lint (fmt) → Validate → Security Scan → Plan → [Manual Approval] → Apply
                                          ↓
                                    Save Plan Artifact
                                          ↓
                                    PR Comment with Diff

Rule: Never use local state in CI/CD. Always configure remote backend before pipeline runs.

Show full SKILL.md (229 more words)Show less

Required Elements

Element	Implementation	Why
AWS Credentials	`aws-actions/configure-aws-credentials@v4` with OIDC	No long-lived secrets
State Backend	S3 + DynamoDB locking	Persistent state, concurrent access protection
Plan Artifact	`terraform plan -out=tfplan` + upload artifact	Ensure apply matches reviewed plan
PR Comment	`actions/github-script` or `terraform-pr-commenter`	Reviewers see changes before merge
Security Scan	`aquasecurity/tfsec-action` or `bridgecrewio/checkov-action`	Catch misconfigurations early
Production Guard	`environment: production` with required reviewers	Human approval before infra changes
Cache	`actions/cache` for `.terraform` directory	Faster init, reduced API calls

GitHub Actions OIDC for AWS

yaml

permissions:
  id-token: write
  contents: read

steps:
  - uses: aws-actions/configure-aws-credentials@v4
    with:
      role-to-arn: ${{ secrets.AWS_ROLE_ARN }}
      aws-region: ${{ vars.AWS_REGION }}

Rule: Always use OIDC federation. Never store AWS access keys as secrets.

Environment Protection

yaml

apply:
  runs-on: ubuntu-latest
  needs: plan
  environment: production  # Requires manual approval
  if: github.ref == 'refs/heads/main' && github.event_name == 'push'

Configure in GitHub: Settings → Environments → production → Required reviewers.

Plan Artifact Pattern

yaml

plan:
  steps:
    - run: terraform plan -out=tfplan
    - uses: actions/upload-artifact@v4
      with:
        name: tfplan
        path: tfplan

apply:
  steps:
    - uses: actions/download-artifact@v4
      with:
        name: tfplan
    - run: terraform apply tfplan

Rule: Apply must use the exact plan that was reviewed, not regenerate it.

IaC Anti-Patterns

apply -auto-approve without environment protection gates
Repeating terraform init in every job without cache
Missing remote state backend configuration
No plan artifact between plan and apply jobs
Skipping security scanning (tfsec, checkov, trivy)
Using latest provider versions instead of pinned versions
Not posting plan output to PR for review

IaC Checklist

Remote state backend configured (S3/GCS/Azure Blob)
State locking enabled (DynamoDB/native)
OIDC federation for cloud credentials
Security scanning in pipeline (tfsec/checkov)
Plan artifact saved and reused in apply
Plan diff posted as PR comment
Environment protection on production
Provider versions pinned in versions.tf
.terraform directory cached between runs

tsh-managing-secrets - For credential configuration
tsh-technical-context-discovering - For finding existing patterns

Files

Just SKILL.md in .github/skills/tsh-implementing-ci-cd of TheSoftwareHouse/copilot-collections.

Open the folder on GitHubat commit 2fbe51e

Compare with similar skills

Tsh Implementing CI CD next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tsh Implementing CI CD compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Tsh Implementing CI CD this skillTheSoftwareHouse/copilot-collections	284	—	~1.6k	Automated safety check: Pass	MIT	3 days ago
AWS Deploymentaws/agent-toolkit-for-aws	2.8k	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit	260	6 repos	~1.1k	Automated safety check: Notes	Custom licence	7 mo ago
Megalinter Checknvuillam/npm-groovy-lint	248	1 repos	~3.9k	Automated safety check: Notes	MIT	4 days ago
Migrate To TeamcityJetBrains/teamcity-cli	125	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
CI CDEliasOulkadi/shokunin	114	—	~3.4k	Automated safety check: Notes	MIT	3 days ago

Similar skills

AWS Deployment
aws/agent-toolkit-for-aws
Official
Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact.
2.8k GitHub stars~1.8k tokensUpdated today
DevOps & CloudAuto-check passed
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
260 GitHub starsUsed in 6 repos~1.1k tokens
DevOps & CloudAuto-check: notes
Megalinter Check
nvuillam/npm-groovy-lint
Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.
248 GitHub starsUsed in 1 repo~3.9k tokens
DevOps & CloudAuto-check: notes
Migrate To Teamcity
JetBrains/teamcity-cli
Official
Migrating CI/CD pipelines to TeamCity. An agent skill from JetBrains/teamcity-cli.
125 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check passed
CI CD
EliasOulkadi/shokunin
Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…
114 GitHub stars~3.4k tokensUpdated 3 days ago
DevOps & CloudAuto-check: notes
Tirith Policies
StackGuardian/tirith
Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…
170 GitHub stars~1.8k tokensUpdated yesterday
DevOps & CloudAuto-check passed

More from TheSoftwareHouse/copilot-collections

All 21 skills in this repo

Tsh Creating Skills
TheSoftwareHouse/copilot-collections
Create new skills (SKILL.md) for GitHub Copilot. An agent skill from TheSoftwareHouse/copilot-collections.
284 GitHub stars~4.1k tokensUpdated 3 days ago
Auto-check passed
Tsh Implementing Frontend
TheSoftwareHouse/copilot-collections
Frontend component patterns, composition, design token integration, barrel file organization, error handling, and Figma-to-code workflow.
284 GitHub stars~2.6k tokensUpdated 3 days ago
Auto-check passed
Tsh Implementing Terraform Modules
TheSoftwareHouse/copilot-collections
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices.
284 GitHub stars~1.6k tokensUpdated 3 days ago
Auto-check passed
Tsh Optimizing Frontend
TheSoftwareHouse/copilot-collections
Frontend rendering optimization, code splitting, memoization strategies, bundle size control, asset optimization, and memory management.
284 GitHub stars~4.1k tokensUpdated 3 days ago
Auto-check passed
Tsh Reviewing Frontend
TheSoftwareHouse/copilot-collections
Frontend-specific code review criteria, component anti-patterns, hooks quality, rendering correctness, accessibility and performance spot-checks, and module organization issues.
284 GitHub stars~4.4k tokensUpdated 3 days ago
Auto-check passed
Tsh Writing Hooks
TheSoftwareHouse/copilot-collections
Custom hook and composable patterns — naming, composition, stable return shapes, lifecycle cleanup, and testing strategies.
284 GitHub stars~3k tokensUpdated 3 days ago
Auto-check passed

Works with

Questions about Tsh Implementing CI CD

What does Tsh Implementing CI CD do?

CI/CD pipeline design patterns and deployment strategies. An agent skill from TheSoftwareHouse/copilot-collections. Tsh Implementing CI CD is an agent skill from TheSoftwareHouse/copilot-collections. CI/CD pipeline design patterns and deployment strategies.

When should I use Tsh Implementing CI CD?

Tsh Implementing CI CD fits situations like: designing pipelines; implementing deployment strategies; setting up automated delivery.

How do I install Tsh Implementing CI CD in Claude Code?

Run `npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a claude-code`. Or copy the skill folder (.github/skills/tsh-implementing-ci-cd in TheSoftwareHouse/copilot-collections) into .claude/skills/tsh-implementing-ci-cd in your project. Claude Code loads it when a task matches its description.

How do I install Tsh Implementing CI CD in Codex?

Run `npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a codex`. Or copy the skill folder (.github/skills/tsh-implementing-ci-cd in TheSoftwareHouse/copilot-collections) into .agents/skills/tsh-implementing-ci-cd in your project. Codex loads it when a task matches its description.

Can I use Tsh Implementing CI CD in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheSoftwareHouse/copilot-collections --skill tsh-implementing-ci-cd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tsh-implementing-ci-cd, .gemini/skills/tsh-implementing-ci-cd, .github/skills/tsh-implementing-ci-cd and .opencode/skills/tsh-implementing-ci-cd in your project.

What does Tsh Implementing CI CD need to run?

Going by SKILL.md and its folder, Tsh Implementing CI CD needs the command-line tools its instructions call (terraform, nx and turbo).

Does Tsh Implementing CI CD access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tsh Implementing CI CD safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tsh Implementing CI CD use?

Tsh Implementing CI CD is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tsh Implementing CI CD use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tsh Implementing CI CD?

Skills that share tags, products or a category with Tsh Implementing CI CD: AWS Deployment (aws/agent-toolkit-for-aws, 2.8k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars) and Migrate To Teamcity (JetBrains/teamcity-cli, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tsh Implementing CI CD?

TheSoftwareHouse (a GitHub organization) maintains it in TheSoftwareHouse/copilot-collections, which has 284 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.

Source: TheSoftwareHouse/copilot-collections on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Tsh Implementing CI CD

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CI/CD Pipeline Patterns

When to Use

Platform Detection

Pipeline Structure

Deployment Strategy Decision

Credentials Strategy Decision

Monorepo Strategy

Process

Checklist

Anti-Patterns

Infrastructure as Code Pipelines

Terraform/Terragrunt Pipeline Structure

Required Elements

GitHub Actions OIDC for AWS

Environment Protection

Plan Artifact Pattern

IaC Anti-Patterns

IaC Checklist

Related Skills

Files

Compare with similar skills

Similar skills

More from TheSoftwareHouse/copilot-collections

Related

Questions about Tsh Implementing CI CD