تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

add-flavor

النجوم٢٬٥٢٠

التفرعات٢٩٩

آخر تحديث٢٤ مايو ٢٠٢٦ في ١٧:٤٤

Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

oxsecurity

oxsecurity/megalinter

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	add-flavor
description	Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.
allowed-tools	Read Grep Glob Bash Edit Write
argument-hint	["flavor-name"]
model	sonnet

Guide through adding a new flavor named $ARGUMENTS.

Steps:

Update the schema enum in megalinter/descriptors/schemas/megalinter-descriptor.jsonschema.json — add the new flavor name to enum_flavors
Create the flavor directory flavors/$ARGUMENTS/
Update descriptors: Add the flavor name to descriptor_flavors arrays in the relevant megalinter/descriptors/*.megalinter-descriptor.yml files for each language/tool this flavor should include
Run make megalinter-build to auto-generate:
- flavors/$ARGUMENTS/Dockerfile
- flavors/$ARGUMENTS/action.yml
- flavors/$ARGUMENTS/flavor.json
Verify the generated Dockerfile includes exactly the intended linters (check flavor.json for the linter list)
Update CHANGELOG.md in the repository root (not docs/) — add one line under Flavors in the beta section:
```
- Add new `<flavor-name>` flavor for <what languages/tools it targets>
```
Branch naming: use user/add-<flavor-name>-flavor

المزيد من هذا المستودع

نفس المستودع

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-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

add-reporter

oxsecurity/megalinter

Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format.

2026-05-242.5k

name	add-flavor
description	Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.
allowed-tools	Read Grep Glob Bash Edit Write
argument-hint	["flavor-name"]
model	sonnet

Guide through adding a new flavor named $ARGUMENTS.

Steps:

Update the schema enum in megalinter/descriptors/schemas/megalinter-descriptor.jsonschema.json — add the new flavor name to enum_flavors
Create the flavor directory flavors/$ARGUMENTS/
Update descriptors: Add the flavor name to descriptor_flavors arrays in the relevant megalinter/descriptors/*.megalinter-descriptor.yml files for each language/tool this flavor should include
Run make megalinter-build to auto-generate:
- flavors/$ARGUMENTS/Dockerfile
- flavors/$ARGUMENTS/action.yml
- flavors/$ARGUMENTS/flavor.json
Verify the generated Dockerfile includes exactly the intended linters (check flavor.json for the linter list)
Update CHANGELOG.md in the repository root (not docs/) — add one line under Flavors in the beta section:
```
- Add new `<flavor-name>` flavor for <what languages/tools it targets>
```
Branch naming: use user/add-<flavor-name>-flavor