Skip to content
TrustedSkillsbeta
Back to all skills

Shellcheck Cicd 2025

Checked
josiahsiegel·vlatest·devops·MIT

Automates ShellCheck integration into CI/CD pipelines, ensuring code quality and security compliance for 2025 standards.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add josiahsiegel/claude-plugin-marketplace --skill shellcheck-cicd-2025 -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

josiahsiegel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    github.comsource host

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a1b1123b9
Manifest
plugins/bash-master/skills/shellcheck-cicd-2025/SKILL.md
Scanned
1 file, 409 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill integrates ShellCheck directly into CI/CD pipelines to automatically scan shell scripts for errors, style issues, and potential security vulnerabilities before code reaches production. It ensures that every script commit triggers an immediate analysis, preventing broken or unsafe automation from entering the deployment workflow.

When to use it

  • You want to enforce strict coding standards across your team's bash or sh scripts without manual reviews.
  • Your CI/CD pipeline fails fast when shell syntax errors or undefined variables are detected in a pull request.
  • You need to identify security anti-patterns, such as using eval or unsafe command substitutions, early in the development cycle.
  • You are automating infrastructure-as-code tasks and require guaranteed script reliability before execution on servers.

Key capabilities

  • Performs static analysis of shell scripts for syntax errors and undefined variables.
  • Detects security vulnerabilities and dangerous command patterns within codebases.
  • Integrates seamlessly into existing GitHub Actions, GitLab CI, or Jenkins workflows.
  • Provides actionable feedback to developers during the pull request review process.

Example prompts

  • "Run ShellCheck on my latest shell script commit and summarize any critical errors found."
  • "Configure a CI/CD pipeline step that blocks merging if ShellCheck detects security vulnerabilities."
  • "Analyze this repository's bash scripts for style inconsistencies and suggest fixes based on ShellCheck rules."

Tips & gotchas

Ensure your CI environment has the shellcheck binary installed or configured as a Docker layer before running the analysis. While highly effective, false positives can occur with complex logic; review warnings rather than treating all output as hard failures unless using strict rule sets.