PHP download

Download the PHP package sandermuller/repo-init without Composer

On this page you can find all versions of the php package sandermuller/repo-init. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download sandermuller/repo-init
More information about sandermuller/repo-init
Files in sandermuller/repo-init

Vendor sandermuller
Package repo-init
Short Description AI playbook + stub library for bootstrapping the canonical Sander/hihaho repo setup. Install globally: `composer global require sandermuller/repo-init`.
License MIT
Homepage https://github.com/sandermuller/repo-init

Keywords bootstrap scaffold laravel ai php-package phpstan-extension rector-extension

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Example code of sandermuller/repo-init

Informations about the package repo-init

sandermuller/repo-init

AI playbook + stub library for bootstrapping the canonical Sander / hihaho dev setup. Pure markdown + stub files. No PHP code in the package itself. Install globally once, use everywhere — same UX as composer global require laravel/installer.

What it does

Walks an AI agent (Claude Code, Cursor, GitHub Copilot, …) through bootstrap, audit, or upgrade of a PHP repo against a canonical baseline:

pint.json, phpstan.neon.dist, phpstan-baseline.neon, rector.php — code-quality tooling
.editorconfig, .gitattributes (with the # >>> package-boost (managed) >>> block — sentinel name preserved for backward compat; owned by package-boost-php), .gitignore
.mcp.json (Laravel-aware categories only — composer-plugin and rector/phpstan extensions skip it)
Shared .github/workflows/{phpstan,pint-check,rector-check,update-changelog}.yml + per-category run-tests.yml + dependabot.yml
tests/Pest.php or phpunit.xml (vendor-driven default)
Per-category extras (testbench.yaml, workbench/, ServiceProvider, extension.neon, src/Plugin.{shape}.php for composer-plugin, etc.)

Install (one-time per machine)

sandermuller/boost-core's global-context auto-sync (active under composer global since 0.2.0) propagates the repo-init skill into ~/.claude/skills/repo-init/, ~/.cursor/skills/repo-init/, ~/.agents/skills/repo-init/, etc. on first install. The skill then auto-activates in any project. See references/boost-core-user-scope.md for the full contract.

Use

Ask Claude (or any agent with the synced skill):

Set up this repo as a Laravel package. Audit this repo against the canonical setup. Upgrade tooling here to current baseline.

The agent reads the repo-init skill, decides intent + category, and opens the matching phase file from $(composer global config home)/vendor/sandermuller/repo-init/phases/. Everything happens in your conversation; nothing is written to your target repo by repo-init itself (the agent does the writes, following the phase's instructions).

Update

boost-core's plugin re-syncs the skill on the same hook.

Repo categories supported

Category	Detection signal
`laravel-project`	`type: project` + `laravel/framework` in `require`
`laravel-package` (sander-style)	`type: library` + `illuminate/*` in `require`
`laravel-package` (spatie-style)	+ `spatie/laravel-package-tools` in `require`
`php-package`	`type: library`, framework-agnostic
`phpstan-extension`	`type: phpstan-extension`
`rector-extension`	`type: rector-extension`
`composer-plugin`	`type: composer-plugin`

Each has its own bootstrap, audit, and upgrade phase file (20 phase files total — 6 audit + 6 upgrade + 8 bootstrap, the extra 2 bootstraps cover filament-plugin and nova-tool which fall through to laravel-package for audit/upgrade). composer-plugin (added in 0.3.0) covers framework-agnostic Composer plugins (e.g. boost-core, package-boost-php) with sub-flags for command-provider / event-subscriber shapes.

What's NOT in the package

No PHP source under src/. No artisan commands, no Symfony Console binary. The agent does all the work.
No state files written to your target repo. No .repo-init-state.json, no .ai/playbooks/repo-init/ copies. Stubs are read in place from the global vendor dir.
No automatic destructive ops. Every overwrite, every dep install, every composer require is gated on a prompt or a documented safety rail (see checklists/per-category-never-touch.md).

Project-local install (escape hatch)

If you want to pin a specific repo-init version per project:

The project-local install takes precedence over the global one. Remove with composer remove --dev sandermuller/repo-init.

Uninstall

Optional skill cleanup (the synced user-level skill dirs survive composer global remove):

(Keep the synced skills if you might re-install later — re-running composer global require sandermuller/repo-init re-syncs them, so leaving them in place is harmless.)

Design

See SPEC.md for the full design (markdown-only + global-install model).

Highlights:

Single entry point — resources/boost/skills/repo-init/SKILL.md.
20 self-contained phase playbooks under phases/.
18 reference docs under per-category-deps.yml).
5 checklists under checklists/.
12 stub trees under stubs/ — shared/ + 2 test-framework variants + 9 categories (composer-plugin, filament-plugin, laravel-package, laravel-package-spatie, laravel-project, nova-tool, php-package, phpstan-extension, rector-extension).

Dependencies

sandermuller/package-boost-php — direct require; ships AI agent skills for PHP package authors.
sandermuller/boost-core — transitive via package-boost-php; Composer plugin engine for vendor/bin/boost sync and the BoostAutoSync::run callback used in post-install-cmd / post-update-cmd.

Both pulled in automatically when you composer global require sandermuller/repo-init.

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md.

Changelog

See CHANGELOG.md.

License

MIT — see LICENSE.

All versions of repo-init with dependencies

PHP Build Version

Package Version

Version 1.5.1 Release 03. Jun 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of repo-init from vendor sandermuller

Requires php Version ^8.3
sandermuller/boost-core Version ^0.19.0

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package sandermuller/repo-init contains the following files

Loading the files please wait ...