lint

Run dotnet format, ESLint, helm lint, and terraform validate across a multi-repo codebase.

2|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill lint-signalbeam-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill lint-signalbeam-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates code quality checks by running multiple linters and formatters across a multi-repo codebase, reporting violations and enabling auto-fixes where available.

Core Features & Use Cases

  • Runs dotnet format, ESLint, helm lint, and terraform validate to identify style, correctness, and security issues.
  • Supports targeted linting by components (backend, frontend, Helm charts, Terraform modules) and optional auto-fix workflows.
  • Useful for CI/CD pipelines and developer workflows to maintain consistent code quality across a multi-repo codebase.

Quick Start

Run lint across the project to detect and optionally fix issues across all supported platforms.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automate linting across .NET, JavaScript, Terraform, and Helm in a multi-repo codebase?

Automate multi-repo linting by running dotnet format, ESLint, helm lint, and terraform validate to identify style, correctness, and security issues across all supported platforms. It enables targeted checks and optional auto-fix workflows in CI/CD pipelines.

Can I run ESLint and dotnet format on specific components instead of the whole project?

Yes, you can run targeted linting by components such as backend, frontend, Helm charts, and Terraform modules. This allows you to execute specific linters like ESLint or dotnet format only on the relevant parts of your multi-repo codebase.

What is the best way to auto-fix code quality violations in a CI/CD workflow?

The best way to auto-fix code quality violations is by invoking dotnet format, ESLint, helm lint, and terraform validate with configurable scope and auto-fix capabilities. This enforces tooling and validation requirements directly within your developer workflows.

Does this unified linting approach enforce conventions for both infrastructure and application code?

Yes, unified linting enforces conventions for both infrastructure and application code by running helm lint and terraform validate alongside dotnet format and ESLint. It maintains consistent code quality across your multi-repo codebase.

Do I need separate linting tools to check Terraform and Helm charts?

No, you do not need separate linting tools to check Terraform and Helm charts. This skill invokes terraform validate and helm lint alongside dotnet format and ESLint to report violations across all supported platforms.