Skip to main content
skill CX Codex

bootstrap-check — Claude Code skill: verify Symfony project setup

bootstrap-check runs a pass/fail check over a Symfony project's setup: .env, services, Doctrine mappings, routes. Each failure comes with the fix.

MIT ★ 234 updated 2026-10-05

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dev-toolings/superpowers-symfony --skill bootstrap-check -a claude-code
Open on GitHub

What bootstrap-check does

The skill walks a Symfony project from the ground up. Does .env exist and carry APP_SECRET with DATABASE_URL? Is vendor/ in place, does bin/console about answer, does the container compile through cache:clear? Then it looks at the database connection and compares the schema against the Doctrine mappings, and lists whatever optional pieces are wired in: API Platform resources, Messenger transports.

The allowed tools are Read, Glob and Grep, so nothing gets edited while the check runs. What you get back is a checklist with each item marked passed or failed, plus the exact command or file to change for every failure, and a note on what was left out of scope.

Order matters. Step two needs vendor/ and a working console, so a fresh clone wants composer install first. Doctrine checks belong on a development database. Secrets from .env stay out of the report, and for cache permission trouble the skill points at ACLs instead of chmod 777.

What it helps with

  • find out why a freshly cloned app refuses to boot
  • check .env for missing bundle variables
  • confirm the container compiles after cache:clear
  • compare the database schema against Doctrine mappings
  • see which Messenger transports and API Platform resources are wired in

Example prompts for the agent

  • Check the bootstrap of this Symfony project: .env, services.yaml, Doctrine — and show me what's broken
  • The container won't compile after cache:clear, run the config check and give me exact fixes
  • List the API Platform resources and Messenger transports this app has

How to install bootstrap-check

1Skills CLI (Vercel)

npx skills add dev-toolings/superpowers-symfony --skill bootstrap-check -a claude-code

2Manually: put the files in place

~/.claude/skills/bootstrap-check/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/bootstrap-check/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about bootstrap-check

How do I install bootstrap-check in Claude Code?

Run npx skills add dev-toolings/superpowers-symfony --skill bootstrap-check -a claude-code. The skill file lands at ~/.claude/skills/bootstrap-check/SKILL.md.

What does bootstrap-check do?

It inspects .env, the installed vendor/, container compilation, the database connection and the schema against Doctrine mappings. You get a checklist of failures with the commands or files that fix them.

Does the skill write to my project?

No. Only Read, Glob and Grep are available to it, so configuration gets read and reported, and the edits stay with you.

Source text

SKILL.md · MIT
---
name: bootstrap-check
description: Verify Symfony project configuration including .env, services.yaml, doctrine settings, and framework requirements
capabilities: [read, search]
tags: [workflow, config]
# projected by `bun run build` — do not edit by hand
allowed-tools:
  - Read
  - Glob
  - Grep
---

# 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`

© dev-toolings · MIT · dev-toolings/superpowers-symfony

Similar skills

All skills for Backend and APIs →

From the same set51

The whole set →
executing-plans The executing-plans skill guides Claude Code through an approved implementation plan, with test-first steps and a separate commit for each one. Use it for multi-step work or to resume after an interruption. CX Codex +1 ★ 234repo stars twig-components twig-components turns repeated Twig markup into Symfony UX components with props, slots and CVA variants. Handy once the same template chunk starts getting copied around. CX Codex +1 ★ 234repo stars cqrs-and-handlers cqrs-and-handlers implements CQRS in Symfony projects using separate Messenger buses for commands and queries. CX Codex +1 ★ 234repo stars daily-workflow The daily-workflow skill lays out a routine for Symfony work, from getting a project running to checking changes before a commit. Use it for migrations, debugging, and recurring maintenance. CX Codex +1 ★ 234repo stars ports-and-adapters ports-and-adapters guides Claude Code in setting up Hexagonal Architecture in Symfony, isolating domain models from Doctrine, HTTP, and vendor SDKs. CX Codex +1 ★ 234repo stars config-env-parameters The config-env-parameters skill guides changes to Symfony environment variables, parameters, and secrets across environments. Use it when configuration needs a clear home and safe injection into the app. CX Codex +1 ★ 234repo stars doctrine-fixtures-foundry doctrine-fixtures-foundry teaches the agent to build Doctrine test data with Zenstruck Foundry v2 factories: named states, sequences and entity relations. Triggers when you write fixtures or migrate factories from Foundry v1. CX Codex +1 ★ 234repo stars doctrine-transactions doctrine-transactions guides Claude Code on managing Doctrine ORM 3 transactions, locking strategies, and flush boundaries in Symfony applications. Fits concurrent row edits and rollback recovery. CX Codex +1 ★ 234repo stars

Project sponsors

Companies that keep this analytics open