Menu
Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | diagnose-config |
| description | Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong. |
| allowed-tools | Read Grep Glob |
| argument-hint | ["config-file-path"] |
| model | sonnet |
Diagnose MegaLinter configuration. Read the .mega-linter.yml (or path provided in $ARGUMENTS) and check for:
.mega-linter.yml, which overrides descriptor defaults. Both .mega-linter.yml and .megalinter.yml are recognized.ENABLE_LINTERS/DISABLE_LINTERS take precedence over ENABLE/DISABLE (descriptor-level). You can't enable a linter if its descriptor is disabled.FILTER_REGEX_INCLUDE/FILTER_REGEX_EXCLUDE regex syntax_ separator matching the generated name DESCRIPTOR_LINTERNAME (e.g., PYTHON_PYLINT_ARGUMENTS, not pylint_arguments)flavors/<flavor>/flavor.jsonPRE_COMMANDS and POST_COMMANDS syntax (each needs command and cwd fields, cwd is root or workspace)_ separator in linter-specific varsVALIDATE_ALL_CODEBASE=true in CI (slow โ usually want diff-only){LINTER}_FILTER_REGEX_INCLUDE/EXCLUDE overrides global filtersReference megalinter/config.py for the full resolution logic.
Run the pr-watch-fix loop in parallel across every open Renovate-bot PR, each in its own git worktree. Use to green-light or triage all dependency-update PRs at once.
Handle CVE/vulnerability reports from security linters (trivy, osv-scanner, etc.). Tries to upgrade first; ignores only when safe and justified; disables an unmaintained linter (with user confirmation) when a dangerous CVE has no fix.
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. Stops cleanly when stuck.
Prepare a MegaLinter release โ update CHANGELOG (prune empty sections, collapse linter versions, backfill PR numbers), run the release build, push commit and tag, and guide GitHub release creation.
Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.
Guided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.