القائمة
Run the MegaLinter build system to regenerate Dockerfiles, test classes, docs, and schemas from YAML descriptors.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/oxsecurity/megalinter --skill buildيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Guided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.
Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the user pastes MegaLinter/CI lint errors and wants them fixed. Applies safe fixes automatically (auto-fix linters first, then guided manual fixes using per-linter fix guides), asks the user when fixing is ambiguous, and can disable rules or linters with user confirmation. Never pushes to the default branch.
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter locally with Docker (full run or fast parallel standalone linter runs).
| name | build |
| description | Run the MegaLinter build system to regenerate Dockerfiles, test classes, docs, and schemas from YAML descriptors. |
| allowed-tools | Bash Read |
| model | haiku |
| metadata | {"internal":true} |
Run the MegaLinter build system. Ask what to build if unclear.
make megalinter-build — regenerate Dockerfiles and test classes from descriptorsmake megalinter-build-with-doc — also regenerate documentation pagesmake megalinter-build-custom — build custom flavorRequires an activated Python venv. If it fails:
make bootstrap to set up the environment (creates venv, installs deps with uv)build.sh manually instead of make, activate venv first:
source .venv/bin/activatesource .venv/Scripts/activate.automation/build.py supports: --doc, --stats, --dependents, --changelog, --release <version>, --version <version>, --latest, --custom-flavor, --delete-dockerfiles, --delete-test-classes.
From YAML descriptors, the build creates:
linters/*/Dockerfile — per-linter Docker imagesflavors/*/Dockerfile, action.yml, flavor.json — flavor Docker imagesmegalinter/tests/test_megalinter/linters/*_test.py — test classesdocs/descriptors/* — documentation pages.automation/generated/ — cached linter versions, helps, licensesIf updating the base image in /Dockerfile, run make megalinter-build and it will propagate to all other Dockerfiles automatically.
Maintainers with write access can comment /build on a PR to trigger the build workflow. Use /help to see all available PR commands.