Verified:GitHub

glab-job

View GitLab CI/CD job details, download artifacts, and retry failed jobs.

Updated Mar 15, 2026

Search Tags:#ci/cd #debugging #pipeline #artifacts #gitlab #jobs

One-click install

npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-job-proyectog007

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-job
Source: https://github.com/ProyectoG007/Skill.bat/tree/main/scripts/05_Dev_Tools/07.%20gitlab-cli-skills-1.11.0/glab-job
Command: npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-job-proyectog007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management and debugging of individual GitLab CI/CD jobs, allowing users to easily view details, retry failures, and access artifacts.

Core Features & Use Cases

Job Inspection: View detailed information about specific CI/CD jobs.
Artifact Management: Download artifacts generated by jobs.
Job Control: Retry or cancel individual jobs.
Log Analysis: View real-time or historical job logs for debugging.
Use Case: When a specific stage in your GitLab pipeline fails, use this Skill to quickly inspect the job logs, identify the error, and retry just that failed job without rerunning the entire pipeline.

Quick Start

Use the glab-job skill to view the details of job with ID 12345.

Frequently Asked Questions about glab-job

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

FAQPage Schema

How do I retry a failed GitLab CI/CD job without rerunning the entire pipeline?▼

To retry a failed GitLab CI/CD job without rerunning the entire pipeline, you can target the specific failed job to trigger a retry. This isolates the job execution, saving pipeline resources and time.

How can I view trace logs for a specific GitLab CI/CD job for debugging?▼

You can view trace logs for a specific GitLab CI/CD job for debugging by retrieving the historical or real-time logs of that individual job. This provides direct access to the specific execution output needed to identify pipeline errors.

What is the best way to download artifacts generated by a GitLab CI/CD job?▼

The best way to download artifacts generated by a GitLab CI/CD job is to interact directly with the specific job that produced them. This method extracts the output files efficiently without requiring a full pipeline scan.

Can I inspect individual GitLab CI/CD job details before canceling a running job?▼

Yes, you can inspect individual GitLab CI/CD job details before canceling a running job. Viewing detailed information about the specific job allows you to verify its state and safely execute a cancellation command.

Does GitLab pipeline troubleshooting require rerunning failed stages to see new errors?▼

GitLab pipeline troubleshooting does not require rerunning failed stages to see new errors. You can access historical trace logs of the failed GitLab CI/CD job to identify the exact error immediately without modifying pipeline state.