Menu
Audit a linter descriptor YAML for completeness, correctness, and best practices. Checks all properties against the full schema.
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
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.
| name | review-descriptor |
| description | Audit a linter descriptor YAML for completeness, correctness, and best practices. Checks all properties against the full schema. |
| allowed-tools | Read Grep Glob Bash WebSearch WebFetch |
| argument-hint | ["descriptor-file-or-linter-name"] |
| model | sonnet |
Review the descriptor for $ARGUMENTS. If a linter name is given, find its descriptor in megalinter/descriptors/.
For each linter entry, audit against the full property list below. Report a checklist with status for each category.
linter_name — present, lowercase, matches CLI executablelinter_url — valid URL to tool docs/websiteexamples — at least 2: one plain, one with config filelinter_text — rich description with features, what it checks, use caseslinter_repo — GitHub/source repository URLlinter_rules_url — URL listing all rules/checkslinter_rules_configuration_url — how to configurelinter_rules_inline_disable_url — how to suppress inlinelinter_rules_ignore_config_url — how to use ignore fileslinter_spdx_license — valid SPDX ID (e.g., MIT, Apache-2.0)linter_speed — rated 1-5 (check if realistic)linter_image_url or linter_icon_png_url or linter_banner_image_url — at least one imagecli_lint_mode — set to file, list_of_files, or projectconfig_file_name — set if linter uses a config filecli_config_arg_name — set if config file is usedcli_lint_fix_arg_name — set if linter supports auto-fixcli_lint_fix_remove_args — set if fix mode requires removing args (e.g., --check)ignore_file_name + cli_lint_ignore_arg_name — set if linter has ignore filescli_version_arg_name — set if not --versioncli_help_arg_name — set if not --helpcli_lint_errors_count — set (regex_count, regex_number, regex_sum, total_lines, or sarif)cli_lint_errors_regex — set and matches actual linter output formatcan_output_sarif: true, cli_sarif_args with {{SARIF_OUTPUT_FILE}}install section with proper renovate-compatible # renovate: datasource=... comments@latest in production)supported_platforms lists linux/amd64 (and linux/arm64 if applicable)install_override for ARM if install differs by platformide.vscode — VS Code extension listed (if one exists; search if unsure)ide.idea — JetBrains/IntelliJ extension listed (if available)eclipse, sublime, emacs, atom, visual_studio.automation/test/<test_folder>/ existscli_lint_errors_regex patternis_formatter — set to true if it's a formatteractivation_rules — set if depends on env vars (e.g., style choice)active_only_if_file_found — set if should only run when config existsdeprecated/disabled — correct if applicabledescriptor_flavors is appropriate for the languageflavors/descriptor_flavors_exclude set if neededAfter the checklist, provide: