- What does leek/laravel-vendor-cleanup do?
- It is a Laravel dev dependency that provides Artisan commands to detect and clean up unchanged vendor-published files such as configs, migrations, views, and lang files. Version 0.13.0 also adds a Laravel Boost skill called vendor-cleanup-audit for AI-assisted auditing and guided cleanup. The core commands remain available without Laravel Boost or an AI agent.
- How do I install leek/laravel-vendor-cleanup?
- Add it as a Composer dev dependency in your Laravel project. If you want the new Boost skill, install Laravel Boost 2.x, run php artisan boost:install, and select leek/laravel-vendor-cleanup in the third-party package picker. Teams not using Boost can keep using the package's Artisan commands after Composer installation.
- Does leek/laravel-vendor-cleanup support my Laravel version?
- The package is built for Laravel applications and is intended as a development tool, but you should verify its Composer constraints against your project's Laravel version before upgrading. The new vendor-cleanup-audit skill specifically requires Laravel Boost 2.x. The core Artisan commands do not depend on Boost.
- What is the vendor-cleanup-audit Laravel Boost skill?
- It is a skill added in v0.13.0 that brings an AI-assisted audit and guided cleanup workflow into Laravel Boost. It uses allowed-tools and a Sonnet subagent in Claude Code, while other agents receive plain numbered questions. It is complementary to the existing Artisan commands and does not affect production runtime.
- How do I install or update the Boost skill after upgrading?
- Run composer update leek/laravel-vendor-cleanup, then run php artisan boost:install or php artisan boost:update. Keep the package selected during the Boost install flow so the new skill files replace the old ones. If you skip that selection step, the skill may not be installed correctly.
- Is AI-assisted vendor cleanup safe?
- The workflow is designed with safeguards: read-only defaults, git rm with explicit file selection, per-file verification through reading, diffing, grepping, and git history, plus a Not confirmed category. Risks remain because an AI agent can misinterpret verification results or users can bypass permission prompts. Review AI-suggested deletions before accepting them and use your normal code review process.
- Can I use leek/laravel-vendor-cleanup without Laravel Boost or Claude Code?
- Yes. The package's core Artisan commands work independently, so teams that do not use Boost or AI agents can continue using them unchanged. The vendor-cleanup-audit skill is optional and can be adopted incrementally. You only need Laravel Boost 2.x if you want the new AI-assisted audit workflow.
- How do I pilot vendor cleanup on a large codebase?
- Start with a scoped audit, for example /vendor-cleanup-audit config view, rather than running a full audit immediately. You can also integrate the package into CI as a read-only report first. Scoping by file type and using the Sonnet subagent for per-file verification helps with throughput on larger projects.
- Does this package affect production deployments or runtime dependencies?
- No, it is a dev dependency intended for local development and audit workflows, not production runtime. It is designed to keep required runtime dependencies intact while identifying unused vendor-published files. Always verify changes in version control before deploying.
- Is leek/laravel-vendor-cleanup actively maintained?
- The package has recent releases and active maintenance signals, including Dependabot squash-merge automation and CI action updates. Maintenance burden is low because it is a dev tool, but you should keep Laravel Boost and any AI tooling updated. Check the GitHub repository for current release notes and compatibility details.