- What’s the difference between package-boost-php and package-boost-laravel?
- package-boost-php is framework-agnostic for any Composer package, while package-boost-laravel includes Laravel-specific skills (e.g., Blade templates, Eloquent queries). Both sync to the same 9 AI agents but target different use cases. Choose based on whether your package depends on Laravel.
- How do I migrate from the deprecated sandermuller/package-boost?
- Run `composer remove sandermuller/package-boost`, then install either `package-boost-php` (agnostic) or `package-boost-laravel` (Laravel-specific) as a dev dependency. Update your `testbench.yaml` to include the new provider and run `vendor/bin/testbench package-boost:sync` to initialize skills.
- Does this work with Laravel 10/11 or only older versions?
- The successors (package-boost-php/laravel) support Laravel 10+ and are framework-agnostic for non-Laravel packages. Legacy 0.15.x only works with older Laravel versions. Always check the successor’s `composer.json` for Laravel version constraints.
- Can I sync skills selectively to specific AI agents (e.g., only GitHub Copilot)?
- Yes. Use `vendor/bin/testbench package-boost:install` to interactively pick agents or pass `--agents=claude,copilot` via CLI. The default syncs to all 9 agents, but selective sync reduces skill bloat for niche use cases.
- Will this break my CI/CD pipeline if I add the --check flag?
- No, the `--check` flag only validates if skills are synced (no runtime impact). Add it to CI as a pre-commit or pre-push step to enforce syncs. Example GitHub Actions: `vendor/bin/testbench package-boost:check --fail-on-drift`.
- Do I need Testbench if my package doesn’t use Laravel?
- Yes, Testbench is required for the sync engine (even for non-Laravel packages). It’s a dev-only dependency with zero runtime overhead. If Testbench isn’t already in your project, add it via `composer require --dev orchestra/testbench` and configure it minimally.
- How do I customize skills beyond the defaults (e.g., add my-package-guidelines.md)?
- Create a `skills/` directory in your package root and add custom `.md` files. Run `vendor/bin/testbench package-boost:doctor` to validate skill names against conflicts. The CLI will auto-detect and sync custom skills during the next sync.
- Are there alternatives to package-boost for Laravel package AI integration?
- For Laravel, `package-boost-laravel` is the direct successor with built-in Laravel skills. Framework-agnostic alternatives include `roave/security-advisories` (for security) or manual `.ai/` setup, but neither offers the same AI-agent sync ecosystem or Testbench integration.
- How does drift detection (--check) work in CI, and can I customize failure behavior?
- The `--check` flag compares your `.ai/skills/` directory against the last synced state. If files are missing or outdated, it exits with code 1. Customize failure behavior via `--fail-on-drift` (default) or `--warn-only` for non-blocking checks.
- What if my package spans multiple Laravel versions (e.g., 8–11)? Should I use ci-matrix-troubleshooting?
- Yes, the `ci-matrix-troubleshooting` skill is designed for cross-version packages. It generates `.github/workflows/` templates for Laravel version matrices. Opt out only if your package targets a single Laravel version to avoid unnecessary complexity.