trunk-validate

Validates trunk-based .NET migrations with six checks covering kustomize builds, pipelines, and production gates.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-validate-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trunk-validate
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/dotnet/skills/trunk-validate
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-validate-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After migrating a .NET API service to trunk-based development with Kustomize and GitLab CI/CD, teams need a systematic way to confirm every piece of the migration is correct before and after merging the MR. This Skill runs six structured validation checks so misconfigurations in kustomize overlays, pipeline jobs, secrets, or production gates are caught early. ## Core Features & Use Cases - Kustomize Build Verification: Builds every region/environment combination and confirms Deployments, Services, IngressRoutes, registries, domains, and security contexts are correct. - Pipeline Component Auditing: Checks .gitlab-ci.yml for required jobs, templates, and conditional components such as Auth0, NuGet, UI tests, EF migrations, and API versioning. - Review App and Secrets Checks: Verifies review overlay templates, gateway HTTPRoute configuration, and secretKeyRef alignment between Kubernetes manifests and GitLab deploy jobs. - Use Case: After running a trunk migration, invoke this Skill with your trunk-migration-config.yaml to get a PASS/FAIL/PENDING checklist across all six validation areas, with guidance to run troubleshooting when issues appear. ## Quick Start Ask the AI to validate the trunk migration using the trunk-migration-config.yaml in the repository root and report the results as a checklist.

Frequently Asked Questions about trunk-validate

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

FAQPage Schema
How do I validate a trunk-based migration for a .NET service?

Run the trunk-validate skill with the path to your trunk-migration-config.yaml, or let it find the file in the repository root. It executes six checks covering kustomize builds, pipeline components, review apps, secrets, main branch pipeline, and production gates, then reports a PASS/FAIL/PENDING checklist.

What does the kustomize build validation check?

It builds every region and environment combination and verifies each output contains a Deployment, Service, and IngressRoute. It also confirms the correct ACR registry, domain, New Relic app name suffix, security context settings, and port 8080 probes.

Does the validation handle optional features like Auth0 or NuGet?

Yes, conditional checks run based on the config decision trees. If auth0, nuget, ui_tests, ef_migrations, or multi-version API support are enabled in the config, the skill verifies the corresponding jobs, images, secret injection, and branch rules in .gitlab-ci.yml.

Why does the main branch pipeline check show as pending?

Validation 5 requires the pipeline to have actually run after the MR merges. If you validate before merging, items like semantic release versioning, git tags, and deployments are reported as pending rather than failed.

What should I do when the validation reports failures?

Review the checklist output to identify which of the six areas failed and the specific issue, such as missing APIM API_IDs. The skill suggests running the trunk-troubleshoot skill with a description of the problem to resolve it.