Run any Skill in Manus with one click

$pwd:

diagnose-config

Name: Diagnose Config
Author: oxsecurity

// Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong.

Run Skill in Manus

$ git log --oneline --stat

stars:2,496

forks:295

updated:May 24, 2026 at 17:44

SKILL.md

readonly

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:

Configuration hierarchy: Env vars override .mega-linter.yml, which overrides descriptor defaults. Both .mega-linter.yml and .megalinter.yml are recognized.
ENABLE/DISABLE conflicts: ENABLE_LINTERS/DISABLE_LINTERS take precedence over ENABLE/DISABLE (descriptor-level). You can't enable a linter if its descriptor is disabled.
Filter patterns: Validate FILTER_REGEX_INCLUDE/FILTER_REGEX_EXCLUDE regex syntax
Linter variable naming: Must be UPPERCASE with _ separator matching the generated name DESCRIPTOR_LINTERNAME (e.g., PYTHON_PYLINT_ARGUMENTS, not pylint_arguments)
Flavor compatibility: If using a flavor image, verify the enabled linters exist in that flavor by checking flavors/<flavor>/flavor.json
EXTENDS: If using remote config inheritance via HTTPS URLs, verify they're accessible
APPLY_FIXES: Check the fix mode is compatible with the CI system — auto-commit requires write access to the branch
Pre/Post commands: Validate PRE_COMMANDS and POST_COMMANDS syntax (each needs command and cwd fields, cwd is root or workspace)
Common mistakes:
- Using lowercase linter names (must be UPPERCASE)
- Missing _ separator in linter-specific vars
- Setting VALIDATE_ALL_CODEBASE=true in CI (slow — usually want diff-only)
- Forgetting {LINTER}_FILTER_REGEX_INCLUDE/EXCLUDE overrides global filters

Reference megalinter/config.py for the full resolution logic.

related-skills.json

same repository

add-flavor.md

from "oxsecurity/megalinter"

Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.

2026-05-242.5k

add-linter.md

from "oxsecurity/megalinter"

Guided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.

2026-05-242.5k

add-reporter.md

from "oxsecurity/megalinter"

Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format.

2026-05-242.5k

analyze.md

from "oxsecurity/megalinter"

Gather requirements for a MegaLinter change by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.

2026-05-242.5k

design.md

from "oxsecurity/megalinter"

Design a MegaLinter solution and write a technical specification. Second step of the contribution workflow, use after /analyze.

2026-05-242.5k

fix-issue.md

from "oxsecurity/megalinter"

End-to-end workflow to fix a GitHub issue — collect context, analyze, implement on a branch, open a PR, then hand off to /pr-watch-fix until CI is green.

2026-05-242.5k

package.json

"author": "oxsecurity"

"repository": "oxsecurity/megalinter"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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:

Configuration hierarchy: Env vars override .mega-linter.yml, which overrides descriptor defaults. Both .mega-linter.yml and .megalinter.yml are recognized.
ENABLE/DISABLE conflicts: ENABLE_LINTERS/DISABLE_LINTERS take precedence over ENABLE/DISABLE (descriptor-level). You can't enable a linter if its descriptor is disabled.
Filter patterns: Validate FILTER_REGEX_INCLUDE/FILTER_REGEX_EXCLUDE regex syntax
Linter variable naming: Must be UPPERCASE with _ separator matching the generated name DESCRIPTOR_LINTERNAME (e.g., PYTHON_PYLINT_ARGUMENTS, not pylint_arguments)
Flavor compatibility: If using a flavor image, verify the enabled linters exist in that flavor by checking flavors/<flavor>/flavor.json
EXTENDS: If using remote config inheritance via HTTPS URLs, verify they're accessible
APPLY_FIXES: Check the fix mode is compatible with the CI system — auto-commit requires write access to the branch
Pre/Post commands: Validate PRE_COMMANDS and POST_COMMANDS syntax (each needs command and cwd fields, cwd is root or workspace)
Common mistakes:
- Using lowercase linter names (must be UPPERCASE)
- Missing _ separator in linter-specific vars
- Setting VALIDATE_ALL_CODEBASE=true in CI (slow — usually want diff-only)
- Forgetting {LINTER}_FILTER_REGEX_INCLUDE/EXCLUDE overrides global filters

Reference megalinter/config.py for the full resolution logic.

diagnose-config

More from this repository

More from this repository