Lint
Skill makigjuro/cloudstack-ai-plugins/plugins/dev-workflow/skills/lint
Claude Code plugin marketplace — AI-powered full-stack cloud engineer for .NET 10 + React 19 + Azure/Terraform/Helm projects. 29 skills, 6 agents, 14 rules.
npx -y skills add makigjuro/cloudstack-ai-plugins --skill lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run all linters and formatters -- dotnet format, ESLint, helm lint, and terraform validate. Use to verify formatting before a PR. Note that hooks auto-fix on save/commit; this skill is for explicit verification across the full codebase. For infrastructure-only changes, use /infra-lint instead.
SKILL.md
3.4 KB, as published. Nobody here has run it
Lint
Run all project linters and report violations. Optionally fix auto-fixable issues.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
SOLUTION=backend.solutionPath(default: find*.sln)FRONTEND_PATH=frontend.path(default:web)CHARTS_PATH=infrastructure.chartsPath(default:deploy/charts)TF_PATH=infrastructure.terraformPath(default:infra/terraform/modules)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Arguments
--fixorfix-- Apply auto-fixes (default: report only)backend-- Only lint C# codefrontend-- Only lint frontend codehelm-- Only lint Helm chartsterraform-- Only lint Terraform/Terragrunt code
If no argument is given, lint everything in report-only mode.
Backend (.NET)
Check formatting violations (report only):
dotnet format {SOLUTION} --verify-no-changes --verbosity normal
Fix formatting violations:
dotnet format {SOLUTION} --verbosity normal
Frontend (React/TypeScript)
Check lint violations (report only):
cd {FRONTEND_PATH} && npm run lint
Fix auto-fixable violations:
cd {FRONTEND_PATH} && npm run lint:fix
Check TypeScript types:
cd {FRONTEND_PATH} && npm run type-check
Helm Charts
Lint all charts in {CHARTS_PATH}/:
# Discover and lint all charts
for chart in $(ls {CHARTS_PATH}/); do
helm lint {CHARTS_PATH}/$chart
done
Template render check (catches template errors without deploying):
for chart in $(ls {CHARTS_PATH}/); do
helm template test {CHARTS_PATH}/$chart > /dev/null
done
Terraform / Terragrunt
Determine the Terraform root directory from {TF_PATH} (e.g., if TF_PATH is infra/terraform/modules, the root for format checks is infra).
Validate Terraform modules:
# Find all Terraform module directories and validate each
for dir in $(find {TF_ROOT} -name "*.tf" -exec dirname {} \; | sort -u); do
echo "=== Validating $dir ==="
terraform -chdir="$dir" init -backend=false -input=false 2>/dev/null
terraform -chdir="$dir" validate
done
Format check (report only):
terraform fmt -check -recursive {TF_ROOT}
Format fix:
terraform fmt -recursive {TF_ROOT}
Terragrunt validate (if terragrunt.hcl files exist):
find {TF_ROOT} -name "terragrunt.hcl" -execdir terragrunt validate \;
After Running
- Report the total violation count for each tool separately.
- For failures, show file path, line number (where available), and rule name.
- If running with
--fix, report how many issues were auto-fixed and how many remain. - If TypeScript type errors exist, list them separately from lint errors.
- Summarize with a pass/fail status per category:
- .NET Format: PASS/FAIL
- ESLint: PASS/FAIL
- TypeScript: PASS/FAIL
- Helm Lint: PASS/FAIL
- Terraform Validate: PASS/FAIL
- Terraform Format: PASS/FAIL