المهارات multi-stage-dockerfile
📦
multi-stage-dockerfile
مراجعة المحتوى r1 آمن ⚙️ الأوامر الخارجية
Create Lean Multi-Stage Dockerfiles
Container images can retain unnecessary build tools and rebuild dependencies too often. This skill guides Dockerfile design with separate build stages, efficient caching, and minimal runtime dependencies.
يدعم: Claude Codex Code(CC)
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
طلب الوكيل
Review the Skillstore skill "multi-stage-dockerfile" from https://skillstore.io/skills/github-multi-stage-dockerfile.md and its manifest at https://skillstore.io/api/skills/github-multi-stage-dockerfile/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "multi-stage-dockerfile". Review a Node.js image that includes build tools and development dependencies at runtime.
النتيجة المتوقعة:
- Use a builder stage to install dependencies and compile the application.
- Keep only production dependencies and required application artifacts in the runtime stage.
- Select a non-root runtime user and verify access to required files.
- Test application startup before comparing final image sizes.
جارٍ استخدام "multi-stage-dockerfile". Dependency installation repeats whenever application source files change.
النتيجة المتوقعة:
- Copy dependency manifests before application source files.
- Install dependencies in an earlier layer to preserve its cache when only source files change.
- Exclude unnecessary files from the build context.
- Compare successive builds to verify cache reuse.
التدقيق الأمني
آمنv1 • ٢٩/٩/٢٠٢٦ فتح التقرير المرتبط بالإصدار
All seven static findings are false positives involving Markdown code spans or defensive Docker guidance. No evidence found of prompt injection, data exfiltration, or malicious execution in SKILL.md. The skill provides instructions, not executable tooling or verified security guarantees.
1
الملفات التي تم فحصها
47
الأسطر التي تم تحليلها
0
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة
عوامل الخطر
⚙️ الأوامر الخارجية (5)
لم يكتشف أحدث تدقيق ثابت ودلالي مكتمل أي نتائج أمنية مؤكدة. ولا يثبت ذلك أن المهارة خالية من الآثار الجانبية.
دقّقه: codex
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/github-multi-stage-dockerfile/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/github-multi-stage-dockerfile?utm_source=security_passport_badge)شارة HTML
<a href="https://skillstore.io/skills/github-multi-stage-dockerfile?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/github-multi-stage-dockerfile/security.svg" alt="Skillstore security assessment" loading="lazy"></a>بطاقة قابلة للتضمين
<iframe src="https://skillstore.io/embed/skills/github-multi-stage-dockerfile.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>الاستشهادات الأكاديمية (APA · BibTeX · CFF)
اقتباس APA
github. (2026). multi-stage-dockerfile security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/github-multi-stage-dockerfile/audits/1اقتباس BibTeX
@techreport{github-github-multi-stage-dockerfile-2026,
author = {github},
title = {multi-stage-dockerfile security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/github-multi-stage-dockerfile/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "multi-stage-dockerfile security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "github"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/github-multi-stage-dockerfile/audits/1"
identifiers:
- type: other
value: "skillstore:github-multi-stage-dockerfile:audit:1"
description: "Skillstore immutable audit report identifier"
تقييم Skillstore
سبب هذا التقييم موثوقية الأدلة: متوسط 55
الهندسة المعمارية
85
قابلية الصيانة
87
المحتوى
65
المجتمع
83
الامتثال للمواصفات
ما الذي يمكنك بناؤه
Containerize an Application
Create separate build and runtime stages while preserving the dependencies and startup behavior an application needs.
Improve CI Build Efficiency
Review dependency installation order and build context contents to reduce avoidable cache invalidation.
Review Runtime Image Hardening
Assess runtime users, file permissions, base image choices, and unnecessary packages before deployment.
جرّب هذه الموجّهات
Start a Multi-Stage Dockerfile
Create a multi-stage Dockerfile for my [language and framework] application. Ask for missing build commands, startup commands, and runtime requirements.
Separate Build and Runtime Dependencies
Review my Dockerfile and separate build dependencies from runtime requirements. Explain which artifacts must be copied and which tools can be excluded.
Optimize Build Caching
Review my Dockerfile and project structure for caching improvements. Suggest layer ordering and build context exclusions, then explain how to test the changes.
Assess Production Readiness
Review my multi-stage Dockerfile for production deployment. Evaluate base image compatibility, non-root permissions, artifact selection, runtime environment settings, and health checks. Identify assumptions requiring verification.
أفضل الممارسات
- Provide build commands, startup requirements, and native dependency constraints before requesting a Dockerfile.
- Build and test the final image, including health checks and non-root file access.
- Use image digests for immutable references and secret mounts for sensitive build credentials.
تجنب
- Copying the entire builder filesystem into the runtime image.
- Choosing Alpine or distroless images without checking dependency and health check compatibility.
- Assuming separate build stages automatically remove secrets from intermediate layers and build caches.
الأسئلة المتكررة
Which assistants can use this skill?
The skill is listed for Claude, Codex, and Claude Code.
Does it support my language or framework?
Its guidance is language-independent. You must supply the build process, runtime requirements, and compatibility constraints for your project.
Does this skill build or scan images automatically?
No. It contains written guidance and recommends vulnerability scanning, but includes no build automation or scanner.
Will a multi-stage build always make my image smaller?
No. Size depends on base images, runtime dependencies, and copied artifacts. Measure the resulting image after testing.
Do explicit version tags guarantee reproducible builds?
No. Tags can change. Use image digests and locked dependencies when you need stronger reproducibility.
Are build secrets safe in a separate builder stage?
Not automatically. Secrets can remain in intermediate layers or caches. Use build secret mounts and avoid embedding credentials in image instructions.