Menu
Update a linter's pinned version in its descriptor YAML. Use when upgrading a linter tool to a new release.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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 | update-linter-version |
| description | Update a linter's pinned version in its descriptor YAML. Use when upgrading a linter tool to a new release. |
Update the version of linter $linter to $version.
Delegation hint — this is a mechanical edit. If you need a sub-agent for the pin change, use
version-bumper(haiku). The build step at the end can be delegated tobuild-runner(haiku).
Steps:
megalinter/descriptors/*.megalinter-descriptor.yml for the linter by nameinstall.dockerfile section (e.g., ARG PIP_TOOL_VERSION=X.Y.Z) or version pin in pip/npm arrays# renovate: datasource=pypi depName=tool-name
ARG PIP_TOOL_VERSION=<new_version>
make megalinter-build to regenerate Dockerfiles with the new versionCHANGELOG.md — linter version upgrades are logged automatically by the auto-upgrade workflow under Linter versions upgradesTEST_KEYWORDS=<linter>_test in the commit message body