Agent skill

Megalinter Fix

by nvuillam in nvuillam/npm-groovy-lint

Fix the errors reported by MegaLinter. An agent skill from nvuillam/npm-groovy-lint.

MITAuto-check: notesDevelopment

Install Megalinter Fix

skills CLI
$ npx skills add nvuillam/npm-groovy-lint --skill megalinter-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nvuillam/npm-groovy-lint megalinter-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nvuillam/npm-groovy-lint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/megalinter-fix .claude/skills/megalinter-fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
megalinter-fix
GitHub stars
248
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
554 words
Files
126
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Fix the errors reported by MegaLinter. An agent skill from nvuillam/npm-groovy-lint.

  • Works in 5 steps: Prepare → Load the fix guides — lazily → Fix → …
  • Pastes MegaLinter/CI lint errors and wants them fixed
  • SKILL.md covers 1. Prepare, 2. Load the fix guides — lazily, 3. Fix and 4. Disabling (always with user…, plus 2 more sections
  • Calls npx and git; needs LINTER_KEY

What it does

Megalinter Fix is an agent skill from nvuillam/npm-groovy-lint. Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the user pastes MegaLinter/CI lint errors and wants them fixed. Applies safe fixes automatically (auto-fix linters first, then guided manual fixes using per-linter fix guides), asks the user when fixing is ambiguous, and can disable rules or linters with user confirmation. Never pushes to the default branch.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 126 other files (for example `linters/README.md`, `linters/action_actionlint.md` and `linters/action_zizmor.md`).

It sits in Development, covering Linting and formatting. The repository describes itself as: Lint, format and auto-fix your Groovy / Jenkinsfile / Gradle files using command line. The licence is MIT.

When your agent uses it

  • Pastes MegaLinter/CI lint errors and wants them fixed
  • Tasks that involve Linting and formatting

Example prompts

  • “/megalinter-fix”

Requirements

  • Node.js
  • A credential in LINTER_KEY
  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Edit, Write, Agent, Skill, AskUserQuestion, WebSearch, WebFetch

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Prepare
  2. Load the fix guides — lazily
  3. Fix
  4. Disabling (always with user confirmation)
  5. Verify and finish

What it can do on your machine

Read from SKILL.md and the folder at commit 2080dff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob
    • Edit
    • Write
    • Agent
    • Skill
    • AskUserQuestion
    • WebSearch

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LINTER_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Megalinter Fix loads about 1.2k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 554 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob, Edit, Write, Agent, Skill, AskUserQuestion, WebSearch, WebFetch

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nvuillam/npm-groovy-lint at commit 2080dff, republished under its MIT licence (© nvuillam). 554 words, ~1,223 tokens.

Download SKILL.mdSave it as .claude/skills/megalinter-fix/SKILL.md (or your agent's skills folder). This skill also uses 125 other files; get the full folder from GitHub.
name
megalinter-fix
description
Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the user pastes MegaLinter/CI lint errors and wants them fixed. Applies safe fixes automatically (auto-fix linters first, then guided manual fixes using per-linter fix guides), asks the user when fixing is ambiguous, and can disable rules or linters with user confirmation. Never pushes to the default branch.
allowed-tools
Bash, Read, Grep, Glob, Edit, Write, Agent, Skill, AskUserQuestion, WebSearch, WebFetch
argument-hint
[linter keys or pasted MegaLinter error list]
user-invocable
true
licence
MegaLinter by OX Security, Copyright 2026 - https://megalinter.io/

MegaLinter fix

Fix the MegaLinter errors you were given (output contract of megalinter-check: linter keys, error counts, files, sample error lines).

1. Prepare

  • If the current branch is the default branch (main/master), create a branch first: git checkout -b megalinter/fix-<topic>.
  • Group the errors by linter key. Handle blocking linters (❌) first; mention non-blocking ones (⚠️) to the user but don't fix them unless asked.

2. Load the fix guides — lazily

For each failing linter only, read its fix guide from this skill's directory: linters/<linter_key_lower>.md (e.g. linters/python_ruff.md). The index is in linters/README.md.

Each guide contains a generated block (auto-fix support, config/ignore files, rule documentation URLs, tuning variables, known non-lint failure patterns) and researched fix instructions. Never load guides for linters without errors.

3. Fix

In this order:

  1. Auto-fixable linters (guide says auto-fix supported): if a container engine is available, run npx mega-linter-runner --linter <KEY> --fix [failing files...] (add --container-engine podman when using podman; use npx mega-linter-runner@beta when .mega-linter.yml pins MEGALINTER_VERSION: beta — see the version rule in megalinter-check). Otherwise apply the underlying tool's documented fix behavior manually. If no engine is installed/running, ask the user first, then follow container-engine.md in the megalinter-check skill directory.
  2. Manual fixes: fix remaining errors file by file following the guide's instructions. Consult the rule documentation URLs when unsure what a rule means.
  3. Errors not covered by the guide (unknown rule, missing/outdated guide): browse the web — fetch the rule's official documentation (start from the URLs in the guide's generated block) or search for the exact error message — before deciding on a fix. Never guess a fix or a suppression syntax.
  4. Ambiguous cases (fix would change behavior, several valid approaches, false positive suspected): ask the user, presenting the options — fix this way, inline-disable with justification, or ignore.
Show full SKILL.md (264 more words)Show less

4. Disabling (always with user confirmation)

When fixing is not relevant (false positives, rule conflicts with project style, linter not applicable):

  • Narrowest first: inline-disable comment on the line → rule exclusion in the linter's config file → <KEY>_FILTER_REGEX_EXCLUDE → <KEY>_DISABLE_ERRORS: true (non-blocking) → DISABLE_LINTERS (last resort).
  • The guide gives the exact syntax for each level. Never disable anything without explicit user confirmation.
  • If a project-mode linter reports unexpected results tied to its exclusions or config resolution, check its console log for [Excluded directories] lines: MegaLinter automatically forwards excluded directories through extra CLI arguments or generated ignore/config files. Disabling that forwarding for the linter (<LINTER_KEY>_FORWARD_EXCLUDED_DIRECTORIES: false) restores the tool's native behavior — useful when the repository's own ignore/config files are already complete.

5. Verify and finish

  1. Re-check with the megalinter-check skill (targeted re-check mode: only the fixed linters/files). Iterate at most 3 times in total.
  2. Show the user a summary: fixed / disabled (with justification) / remaining.
  3. Commit on the working branch with a clear message. Ask before pushing; never push to the default branch.

Optimization: sub-agents (Claude Code and compatible agents)

If sub-agents are available and megalinter-fixer is installed (see megalinter-setup), fan out one megalinter-fixer per failing linter in parallel, giving each: the linter key, its error list, and the content of its fix guide. Each fixer returns its fixed count, modified files, and an unresolved list (possibly containing proposed_disable suppressions — fixers never apply disables themselves). Consolidate, ask the user about every unresolved item and proposed disable, apply the confirmed ones yourself, then run the targeted re-check (via megalinter-runner agents when available).

Without sub-agents, fix linters sequentially inline.

© nvuillam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 125 other files in .claude/skills/megalinter-fix of nvuillam/npm-groovy-lint.

  • SKILL.md
  • linters/README.md
  • linters/action_actionlint.md
  • linters/action_zizmor.md
  • linters/ansible_ansible_lint.md
  • linters/arm_arm_ttk.md
  • linters/bash_exec.md
  • linters/bash_shellcheck.md
  • linters/bash_shfmt.md
  • linters/bicep_bicep_linter.md
  • linters/c_clang_format.md
  • linters/c_cppcheck.md
  • linters/c_cpplint.md
  • linters/clojure_clj_kondo.md
  • linters/clojure_cljstyle.md
  • linters/cloudformation_cfn_lint.md
  • linters/coffee_coffeelint.md
  • linters/copypaste_jscpd.md
  • linters/cpp_clang_format.md
  • linters/cpp_cppcheck.md
  • … and 106 more

Open the folder on GitHubat commit 2080dff

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nvuillam/npm-groovy-lint, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Megalinter Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Megalinter Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Megalinter Fix this skillnvuillam/npm-groovy-lint2481 repos~1.2kAutomated safety check: NotesMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.3k1 repos~2.2kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k1 repos~2.2kAutomated safety check: PassMIT
Minimizing Ty Ecosystem Changesastral-sh/ruff50k—~4.6kAutomated safety check: PassMIT
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.3k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed
  • Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed
  • Official

    A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…

    50k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from nvuillam/npm-groovy-lint

  • Megalinter Check

    nvuillam/npm-groovy-lint

    Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check: notes
  • Megalinter Setup

    nvuillam/npm-groovy-lint

    Install or upgrade MegaLinter on a repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check: notes
  • Megalinter

    nvuillam/npm-groovy-lint

    Entry point for everything MegaLinter. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~915 tokens
    Auto-check: notes
  • Upgrade Java Deps

    nvuillam/npm-groovy-lint

    Upgrade CodeNarc and the bundled Java dependencies (jackson, logback, slf4j, janino, GMetrics, Groovy libs) that ship inside lib/java/, rebuild the deterministic CodeNarcServer.jar, and verify…

    248 GitHub stars~1.9k tokensUpdated 4 days ago
    Auto-check: notes
  • PR Watch Fix

    nvuillam/npm-groovy-lint

    Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing.

    248 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes

Categories

Questions about Megalinter Fix

What does Megalinter Fix do?

Fix the errors reported by MegaLinter. An agent skill from nvuillam/npm-groovy-lint. Megalinter Fix is an agent skill from nvuillam/npm-groovy-lint. Fix the errors reported by MegaLinter.

When should I use Megalinter Fix?

Megalinter Fix fits situations like: pastes MegaLinter/CI lint errors and wants them fixed; tasks that involve Linting and formatting.

How do I install Megalinter Fix in Claude Code?

Run `npx skills add nvuillam/npm-groovy-lint --skill megalinter-fix -a claude-code`. Or copy the skill folder (.claude/skills/megalinter-fix in nvuillam/npm-groovy-lint) into .claude/skills/megalinter-fix in your project. Claude Code loads it when a task matches its description.

How do I install Megalinter Fix in Codex?

Run `npx skills add nvuillam/npm-groovy-lint --skill megalinter-fix -a codex`. Or copy the skill folder (.claude/skills/megalinter-fix in nvuillam/npm-groovy-lint) into .agents/skills/megalinter-fix in your project. Codex loads it when a task matches its description.

Can I use Megalinter Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nvuillam/npm-groovy-lint --skill megalinter-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/megalinter-fix, .gemini/skills/megalinter-fix, .github/skills/megalinter-fix and .opencode/skills/megalinter-fix in your project.

What does Megalinter Fix need to run?

Going by SKILL.md and its folder, Megalinter Fix needs the command-line tools its instructions call (npx and git) and credentials named LINTER_KEY. Our summary lists: Node.js; A credential in LINTER_KEY. Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Edit, Write, Agent, Skill, AskUserQuestion, WebSearch, WebFetch.

Does Megalinter Fix access the network?

SKILL.md contains no URLs. Its commands use npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Megalinter Fix safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Megalinter Fix use?

Megalinter Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Megalinter Fix use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Megalinter Fix?

Skills that share tags, products or a category with Megalinter Fix: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Summarise Ecosystem Results (astral-sh/ruff, 50k stars), Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars) and Babysit PR To Pass CI (sgl-project/sglang, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Megalinter Fix?

nvuillam (a GitHub user) maintains it in nvuillam/npm-groovy-lint, which has 248 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 4, 2026.

Source: nvuillam/npm-groovy-lint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.