Ioc github actions

Skill pngdeity/apm-user-repository/packages/ci-cd-standards/.apm/skills/ioc-github-actions

Personal APM marketplace — skills, prompts, agents, and instructions for AI coding agents

Install

npx -y skills add pngdeity/apm-user-repository --skill ioc-github-actions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Inversion of Control CI/CD pipeline architecture. Use when designing or refactoring CI/CD pipelines to extract domain logic into testable shell scripts.

SKILL.md

2.9 KB, as published. Nobody here has run it

Inversion of Control CI/CD Pipeline

An architectural pattern that treats the CI/CD platform as a dumb orchestrator. All domain logic, dependency management, and compilation instructions are extracted into standard shell scripts housed within the repository.

The Contract

The CI/CD platform runs a single entrypoint script. The framework file (e.g., .github/workflows/build-deploy.yaml) defines only triggers and artifact routing. Build logic lives entirely in version-controlled scripts.

Key Benefits

Local Parity: Because execution logic resides in standard shell scripts, the entire pipeline can be run, tested, and debugged natively on a local machine prior to pushing to the CI runner.
Vendor Independence: Migrating CI providers requires updating only the thin orchestrator file — zero changes to build logic.
Testability: Shell scripts are independently testable without invoking the CI platform.

Implementation Pattern

Orchestrator File

The CI platform file defines triggers and delegates execution:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - run: ./ci/build.sh
      - uses: actions/upload-artifact@v7
        with:
          path: ./ci/out/

Bootstrapper Script Pattern

ci/
├── build.sh           # Main entrypoint, sequences the pipeline
├── setup-env.sh        # Bootstraps runner environment (downloads tooling into ./ci/bin/)
├── execute-build.sh    # Handles compilation and standardizes output into ./ci/out/
└── out/                # Standardized artifact output directory

Design Rules

Single entrypoint. The CI file runs exactly one script.
Isolated tooling. Fetch build dependencies into a local directory (./ci/bin/) rather than assuming global installation.
Standardized output. All build artifacts land in a single directory (./ci/out/) for consistent artifact upload.
Execution permissions. Ensure all shell scripts have execution permissions (chmod +x ci/*.sh) before committing.

Migration Pattern

When migrating from an imperative CI file to IoC:

Identify all inline shell commands in the existing CI YAML
Extract each logical group into a named script under ci/
Replace inline commands with script invocations in the CI YAML
Verify local parity by running ./ci/build.sh from the project root
Push and monitor the CI console for any missing dependency errors

Future Containerization

The IoC contract guarantees that migrating the pipeline to a containerized build (Docker, CNCF Buildpacks) requires zero changes to the CI platform YAML file. The entrypoint script is replaced with a container invocation; the orchestrator remains unchanged.