lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

5.3k|516|Updated Dec 26, 2024
One-click install
npx skills add https://github.com/aaddrick/claude-desktop-debian --skill lint-aaddrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/aaddrick/claude-desktop-debian/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/aaddrick/claude-desktop-debian --skill lint-aaddrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of checking your code for common errors and style issues, preventing bugs and maintaining consistency before you commit.

Core Features & Use Cases

  • Shell Script Linting: Uses shellcheck to find errors in .sh files.
  • GitHub Actions Workflow Linting: Uses actionlint to validate .yaml workflow files.
  • Use Case: Before pushing changes to a shared repository, run this Skill to catch any syntax errors or potential problems in your scripts and CI configurations.

Quick Start

Run linting checks on changed shell scripts and GitHub Actions workflows.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I lint shell scripts and GitHub Actions workflows to prevent CI failures?

Static analysis for shell scripts and GitHub Actions workflows works by parsing script and workflow syntax using shellcheck and actionlint to identify potential errors and enforce coding standards during software development workflows.

How do I check my shell scripts for common errors before pushing to a shared repository?

You can check shell scripts for common errors before pushing by running static analysis with shellcheck, which parses .sh files to find syntax errors and style issues, maintaining consistency in your codebase.

Can I validate GitHub Actions workflow YAML files for potential configuration errors?

Yes, you can validate GitHub Actions workflow YAML files for configuration errors using actionlint, which parses and validates workflow syntax to ensure your CI/CD pipeline configurations are correct before deployment.

Do I need shellcheck and actionlint installed to parse and validate script syntax?

Yes, this static analysis process requires shellcheck and actionlint to parse and validate script and workflow syntax, enabling code quality assurance and CI/CD pipeline validation for your software development workflows.

What is the best way to enforce coding standards across shell scripts and CI/CD pipeline configurations?

The best way to enforce coding standards across shell scripts and CI/CD configurations is automated static analysis, using shellcheck for .sh files and actionlint for .yaml workflows to catch potential errors before committing.