atomic-framework-cli-entrypoint

Create a root-level CLI entrypoint that boots Composer autoload and bootstrap/app.php.

9|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/MADEVAL/Atomic-Framework-Skills --skill atomic-framework-cli-entrypoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atomic-framework-cli-entrypoint
Source: https://github.com/MADEVAL/Atomic-Framework-Skills/tree/main/atomic-framework-cli-entrypoint
Command: npx skills add https://github.com/MADEVAL/Atomic-Framework-Skills --skill atomic-framework-cli-entrypoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty around the project-root CLI stub by defining the exact executable entrypoint Atomic Framework expects for running console commands.

Core Features & Use Cases

  • Minimal Bootstrap Flow: Loads Composer autoload, starts the framework bootstrap, and hands off command execution to the application instance.
  • Direct CLI Execution: Supports running the command runner through either php atomic or the executable ./atomic file.
  • Implementation Reference: Shows the exact root-level script structure needed for a reliable entrypoint, including timing initialization and exit status propagation.

Quick Start

Use this Skill to verify or create the project-root atomic entrypoint that loads Composer, boots bootstrap/app.php, and delegates to the framework command handler.

Frequently Asked Questions about atomic-framework-cli-entrypoint

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

FAQPage Schema
How do I create a PHP CLI entrypoint that boots Composer autoload and runs console commands?

A PHP CLI entrypoint for console commands requires a minimal executable script with a shebang, ATOMIC_START timing initialization, Composer vendor autoload loading, bootstrap/app.php returning an application instance, and proper exit status propagation.

What does the atomic bootstrap file need to load before executing framework commands?

The atomic bootstrap file needs to load Composer vendor autoload and require bootstrap/app.php, which must return an application instance that handles the console command execution and propagates the exit status.

Can I run Atomic Framework CLI commands directly without calling php explicitly?

Yes, you can execute Atomic Framework CLI commands directly using the executable ./atomic file or by invoking php atomic, both of which trigger the root-level stub to boot the application and run the console handler.

Why does my Atomic Framework CLI script not propagate the correct exit status?

Exit status propagation fails when the CLI entrypoint script does not properly return the exit code from the application instance after running console commands through the framework handler during the bootstrap flow.

Do I need Composer to set up the Atomic Framework CLI entrypoint?

Yes, Composer is required because the CLI entrypoint script directly loads the Composer vendor autoload file to initialize dependencies before booting bootstrap/app.php and running console commands.

What is the minimal script structure for an Atomic Framework executable stub?

The minimal executable stub structure includes a PHP shebang, ATOMIC_START timing initialization, Composer autoload loading, bootstrap/app.php inclusion returning an application instance, and final exit status propagation.