Verified:GitHub

tg-migrate-pipeline

Generates GitLab CI/CD pipeline configuration and ci-local-vars for Terragrunt migrations.

Updated Jul 22, 2026

Search Tags:#migration #infrastructure #pipeline #gitlab-ci #ci-cd #terragrunt #gitlab-ci-local

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-pipeline-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: tg-migrate-pipeline
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/terragrunt-migrate/skills/tg-migrate-pipeline
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-pipeline-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completing a Terragrunt repository migration requires a working CI/CD pipeline, but hand-writing a .gitlab-ci.yml covering 13 environments and setting up local testing variables is error-prone and repetitive. ## Core Features & Use Cases - Pipeline Generation: Creates a .gitlab-ci.yml referencing the shared Terragrunt pipeline template from devsecops/terraform-modules, covering all 13 standard environments. - Local CI Testing Support: Optionally generates a ci-local-vars directory with global.yml and per-environment YAML files for gitlab-ci-local runs. - Use Case: As the final phase of a Terragrunt repo migration, run this phase to produce the pipeline config, review it, and commit the fully migrated repository. ## Quick Start Run the tg-migrate-pipeline phase with the target repository path and GitLab project ID to generate the pipeline configuration for my migrated Terragrunt repo.

Frequently Asked Questions about tg-migrate-pipeline

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

FAQPage Schema

How do I generate a GitLab CI pipeline for a Terragrunt repository?▼

Run this migration phase with the target repository path to generate a .gitlab-ci.yml covering all 13 standard environments. The generated pipeline references the shared Terragrunt pipeline template from devsecops/terraform-modules.

How do I test a GitLab pipeline locally with gitlab-ci-local?▼

Generate the ci-local-vars directory containing global.yml and per-environment YAML files, then pass them to gitlab-ci-local with --variables-file flags. Ignore predefined variables like CI_COMMIT_BRANCH and CI_DEFAULT_BRANCH when running locally.

What is the GitLab project ID used for in pipeline generation?▼

The numeric GitLab project ID is required for generating ci-local-vars, since the process fetches CI/CD variables defined on the project. If you do not provide it as an argument, the assistant will ask for it.

Can I skip generating ci-local-vars during pipeline setup?▼

Yes, ci-local-vars generation is optional. The assistant asks whether you want local CI testing support, and only creates the global.yml and per-environment variable files if you confirm.

When should the pipeline cutover phase run in a Terragrunt migration?▼

It is Phase 6, the final phase before the migrated repository is ready to commit. Run it after earlier migration phases complete, then review the generated .gitlab-ci.yml and commit the repository.