mcpField
B
bootstrap-check

bootstrap-check

github.com/dev-toolingsDevelopment22782 installsUpdated 3w ago
Repository

About bootstrap-check

bootstrap-check is a read-only checklist skill for validating the setup of Symfony applications, especially unfamiliar or newly cloned projects. It checks environment variables, dependencies, boot and container compilation, database mappings, and optional API Platform or Messenger components.

Key features

  1. 01Checks required environment variables
  2. 02Verifies dependencies and application boot
  3. 03Compiles the container and lists services and routes
  4. 04Checks database connection and schema mappings
  5. 05Inspects optional API Platform and Messenger setup

Use cases

  1. 01Assessing a freshly cloned Symfony project
  2. 02Investigating application boot or container errors
  3. 03Checking configuration before making changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dev-toolings/superpowers-symfony --skill bootstrap-check

After installing, type/bootstrap-checkin Claude Code to confirm it loaded.

Bundled filesreference.md

Details

From the project README

Bootstrap Check (Symfony)

Use when

  • Starting work on an unfamiliar or freshly cloned Symfony project.
  • The application fails to boot, the container does not compile, or routes are missing.
  • Checking .env, config/packages/*, Doctrine, API Platform or Messenger setup before a change.

Default workflow

  1. Confirm .env exists and defines APP_SECRET, DATABASE_URL and the variables the bundles need.
  2. Confirm vendor/ is installed and bin/console about runs.
  3. Compile the container (cache:clear) and list services and routes.
  4. Check the database connection and that the schema matches the mappings.
  5. Check the optional stacks present: API Platform resources, Messenger transports.

Guardrails

  • Read only: report what is missing, do not rewrite configuration while checking.
  • Never print secret values from .env or the vault.
  • Prefer ACLs or the correct user over chmod 777 for cache permission issues.
  • Run Doctrine checks against a development database, never production.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • The checklist with each item passed or failed.
  • The exact fix for each failure (command or file to change).
  • What was not checked, and why.

References

  • reference.md

Comments

Markdown supported