jenkinsfile-validator

Validate Jenkins pipeline and shared library syntax, structure, and security.

7|3|Updated May 4, 2026
One-click install
npx skills add https://github.com/nopperabbo/codebuddy2api --skill jenkinsfile-validator-nopperabbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jenkinsfile-validator
Source: https://github.com/nopperabbo/codebuddy2api/tree/main/opencode-config/skills/_archived/jenkinsfile-validator
Command: npx skills add https://github.com/nopperabbo/codebuddy2api --skill jenkinsfile-validator-nopperabbo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Jenkins pipelines and shared libraries often suffer from syntax errors, structural issues, and security gaps that slip into CI/CD workflows; this skill provides a local validation workflow to detect and surface these problems early.

Core Features & Use Cases

  • Syntax validation for Declarative and Scripted pipelines
  • Structural validation of stages, steps, parallel blocks, and shared libraries
  • Security checks for credential handling and best-practice patterns
  • Preflight/documentation enrichment via local references to common plugins and docs
  • Use cases include validating Jenkinsfiles in PRs, auditing legacy pipelines, and ensuring pipeline maintainability

Quick Start

Run the validator against your Jenkinsfile path to perform full syntax, security, and best-practices checks

Frequently Asked Questions about jenkinsfile-validator

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

FAQPage Schema
How do I validate a Jenkinsfile locally before committing it to a CI/CD pipeline?

To validate Jenkins pipelines locally, run the validator against your Jenkinsfile path to perform full syntax, security, and best-practices checks without pushing to a remote CI/CD server.

What types of Jenkins pipelines can be checked for syntax and structure errors?

Both Declarative and Scripted Jenkins pipelines can be checked, along with shared library components, to identify structural issues in stages, steps, and parallel blocks.

Can I use this Jenkinsfile validator to audit security and credential handling?

Yes, you can audit Jenkins pipeline security by running validation checks that specifically target credential handling and best-practice patterns to prevent security gaps.

Do I need jq installed to perform structural validation on Jenkins shared libraries?

Bash-based tooling like grep, sed, and awk is required for Jenkins shared library validation, while jq is an optional dependency that enables enhanced validation features.

What is the best way to lint Jenkins shared libraries in pull requests?

The best way to lint Jenkins shared libraries in pull requests is to run an automated local validator that surfaces syntax, structural, and security issues before merging.