一键在 Manus 中运行任何 Skill

diagnose-config

星标2,520

分支299

更新时间2026年5月24日 17:44

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

oxsecurity

oxsecurity/megalinter

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

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.

同仓库更多 Skills

同仓库

pr-watch-fix-renovate

oxsecurity/megalinter

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.

2026-07-052.5k

fix-security-issue

oxsecurity/megalinter

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.

2026-07-052.5k

pr-watch-fix

oxsecurity/megalinter

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.

2026-07-052.5k

prepare-release

oxsecurity/megalinter

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.

2026-06-282.5k

add-flavor

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

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

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.