oxsecurity/megalinter

oxsecurity/megalinter

Agent Claude Code

Gather requirements for a MegaLinter change by asking clarifying questions until the problem is fully understood. Use before designing or implementing any change.

oxsecurity/megalinter

Agent Claude Code

Run and troubleshoot the MegaLinter build system that generates Dockerfiles, documentation, test classes, and schemas from YAML descriptors.

oxsecurity/megalinter

Agent Claude Code

Review MegaLinter Python code changes for quality, conventions, and correctness. Use after writing or modifying Python code in the megalinter package.

oxsecurity/megalinter

Agent Claude Code

Specialist for creating, editing, and validating MegaLinter YAML descriptor files. Use when working on linter descriptors, adding new linters, or modifying linter configurations.

oxsecurity/megalinter

Agent Claude Code

Design a MegaLinter solution and write a technical specification based on requirements analysis. Use after /analyze.

oxsecurity/megalinter

Agent Claude Code

Implement MegaLinter code changes following a technical specification or direct request. Use after /design, or directly for small focused changes.

oxsecurity/megalinter

Agent Claude Code

Poll a GitHub PR's CI status, classify failed jobs, and fetch the relevant log excerpts. Use to gather data about a PR's check state — does NOT decide fixes or edit code.

oxsecurity/megalinter

Agent Claude Code

Analyze a CVE or vulnerability finding (from trivy, osv-scanner, grype, etc.) to determine whether it applies to MegaLinter, the right remediation (upgrade vs. ignore), and the justification. Use when judgment calls on safety, exploitability, or scope are required.

oxsecurity/megalinter

Agent Claude Code

Debug failing MegaLinter linter tests. Use when tests fail, test fixtures need fixing, or Docker-based test execution needs troubleshooting.

oxsecurity/megalinter

Agent Claude Code

Build, lint, and run MegaLinter tests inside Docker to verify the implementation. Use after /implement.

oxsecurity/megalinter

Agent Claude Code

Mechanically bump a pinned tool/linter version in a YAML descriptor or Dockerfile ARG. Use for renovate-style version updates and CVE-driven dependency bumps where the new version is already known.

oxsecurity/megalinter

Agent

Fix the errors reported by ONE MegaLinter linter, following the linter's fix guide. Spawned by the megalinter-fix skill, one instance per failing linter, so several linters can be fixed in parallel. Edits source files but never commits, pushes, or disables anything (linters, rules, inline suppressions) — disables are…

oxsecurity/megalinter

Agent

Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.

oxsecurity/megalinter

Agent

Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.

oxsecurity/megalinter

Agent

The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.