Verified:GitHub

pipeline-edit

Applies GitLab CI editing rules for jobs, stages, needs, and dependencies in .gitlab-ci.yml files.

Updated Jul 22, 2026

Search Tags:#devops #yaml #pipeline #continuous integration #gitlab-ci #ci-cd #job dependencies

One-click install

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

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Editing GitLab CI pipelines often leads to misused `needs` and `dependencies` keywords, causing broken pipelines or missing artifacts. This Skill provides concise, enforceable rules so pipeline edits follow GitLab CI best practices. ## Core Features & Use Cases - Auto-triggered guidance: Activates on phrases like "update pipeline", "add job", or "new stage" to inject editing rules into context. - Needs vs dependencies decision rule: Enforces a simple check—use `needs` only for same-stage dependencies, otherwise use `dependencies` for artifacts. - Reference documentation: Loads core rules from a references file and points to `/gitlab-ci:standards-load` for comprehensive checklists. - Use Case: When asked to add a new job to `.gitlab-ci.yml`, the Skill ensures the job's stage placement and dependency keywords follow the correct GitLab CI semantics before the edit is made. ## Quick Start Ask the assistant to add a new job or stage to your .gitlab-ci.yml pipeline and the editing guidelines will be applied automatically.

Frequently Asked Questions about pipeline-edit

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

FAQPage Schema

How do I add a new job to a GitLab CI pipeline correctly?▼

Add the job to .gitlab-ci.yml with an appropriate stage, then decide on dependencies: use `needs` only if the dependency is in the same stage, otherwise use `dependencies` when you need artifacts from another stage.

When should I use needs vs dependencies in GitLab CI?▼

Use `needs` when the dependent job is in the same stage as the current job. If the dependency is in a different stage, do not use `needs`; use `dependencies` instead when you need to download artifacts from that job.

Does this Skill trigger automatically when editing gitlab-ci files?▼

Yes, it auto-triggers on phrases like "update pipeline", "modify gitlab-ci", "add job", or "new stage". It is not user-invocable directly, but loads guidance into context when pipeline editing is detected.

Where can I find detailed GitLab CI pipeline standards and checklists?▼

The Skill references a core-rules document for essential guidance. For comprehensive documentation with detailed examples and checklists, run the /gitlab-ci:standards-load command.

What are the limitations of these pipeline editing guidelines?▼

The Skill provides lightweight core rules only, focused mainly on the needs versus dependencies decision. Complex pipeline architectures, security scanning gates, and full audits require the separate standards-load and standards-audit commands.