wf-docker-environment-readiness-method

Name: wf-docker-environment-readiness-method
Availability: InStock
Author: belluga

Validate repository symlinks, submodules, and permissions before DevOps tasks.

Updated Nov 7, 2025

Search Tags:#devops #verification #permissions #symlinks #submodules #environment-readiness

Ready to run

npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-environment-readiness-method

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wf-docker-environment-readiness-method
Source: https://github.com/belluga/delphi-ai/tree/main/skills/wf-docker-environment-readiness-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-environment-readiness-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill ensures the working copy is correctly wired (symlinks, scripts, submodules, permissions, README steps) before executing DevOps or CI/CD tasks. It favors deterministic script checks to prevent drift and misconfigurations.

Core Features & Use Cases

Deterministic readiness checks that verify symlinks, submodules, and required folders before any DevOps task.
Readiness reports and adherence checking with canonical Delphi/PACED tooling to surface drift and misconfigurations before builds.
Scope-aware applicability: effective during Genesis zero-state bootstrap and before downstream DevOps tasks that rely on a correctly wired workspace.

Quick Start

Run the environment readiness checks before starting DevOps work to guarantee the repository is correctly wired.

Frequently Asked Questions about wf-docker-environment-readiness-method

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify symlinks and submodules for CI environment readiness?▼

You can verify environment readiness by running deterministic scripts like verify_context.sh and verify_environment.sh to check symlinks, submodule status, and directory permissions before starting CI work.

What is environment readiness verification in a DevOps workflow?▼

Environment readiness verification is the process of using deterministic script checks to surface drift, validate foundation_documentation submodules, and ensure the repository workspace is correctly wired before executing DevOps tasks.

When do I need to run environment readiness checks on my repository?▼

Run environment readiness checks during the zero-state Genesis bootstrap and immediately before any downstream DevOps tasks to guarantee the working copy has correct symlinks, submodules, and folder permissions.

Does this readiness check validate directory permissions and submodule status?▼

Yes, the readiness checks explicitly validate directory permissions, submodule status, and symlink configurations to surface misconfigurations and prevent workspace drift before builds.

What's the best way to prevent repository drift before running DevOps tasks?▼

The best way to prevent drift is applying canonical readiness scripts that enforce deterministic environment checks across symlinks, submodules, and permissions, ensuring consistent workspace configuration before DevOps execution.

Why is my CI pipeline failing due to misconfigured symlinks or missing submodules?▼

CI pipelines fail when the working copy is incorrectly wired, but running canonical readiness scripts detects missing foundation_documentation submodules and symlink drift early, preventing pipeline failures.