Download the PHP package akurbanov/dev-tools without Composer
On this page you can find all versions of the php package akurbanov/dev-tools. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download akurbanov/dev-tools
More information about akurbanov/dev-tools
Files in akurbanov/dev-tools
Package dev-tools
Short Description Pre-commit checks and a project snapshot for coding agents: dev:check, dev:brief and a test-database guard
License MIT
Homepage https://github.com/2rkmen/dev-tools
FAQ
Example:
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 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.
Informations about the package dev-tools
akurbanov/dev-tools
Русская версия
Pre-commit checks and a project snapshot for coding agents (Claude Code, Codex) in Laravel projects. Install it as a dev dependency.
An agent starts every session by rebuilding the same picture of the project —
versions, packages, schedule, git state — and ends it by running the same
chain of checks, each time with a different tail. Both are deterministic,
so this package does them in one command and prints a short report instead of
a wall of output.
Heads up: command output and the source docblocks are in Russian.
Install
The service provider is picked up by package discovery and the commands are
registered in the console only. Nothing ships to production — the package
lives in require-dev.
Requires PHP 8.2+ and Laravel 11, 12 or 13.
Commands
dev:check prints one line per step and, for a failed step, only the part of
the output that explains the failure: for tests, everything from the first
failing test to the summary; for the JSON output of laravel/pao, a list of
file:line — test — message.
Steps do not abort each other, so a single run shows everything that needs fixing. The exception is the database guard: if it fails, the tests are not run at all.
Before running tests dev:check clears the config cache and checks the test
database declared in phpunit.xml (falling back to .env). Child processes
do not inherit the variables artisan loaded from .env, so tests run in the
same environment they would get from a bare shell.
Test database guard
Tests refuse to run when APP_ENV is not testing, when the database is
neither sqlite :memory: nor named like test_*, *_test or *_testing,
or when the host is not local. The guard inspects the live connection rather
than phpunit.xml: a setting can be overridden by an environment variable or
a stale config cache, a connection cannot.
Patterns and hosts live in config/dev-tools.php:
Development
License
MIT — see LICENSE.
All versions of dev-tools with dependencies
illuminate/console Version ^11.0|^12.0|^13.0
illuminate/database Version ^11.0|^12.0|^13.0
illuminate/process Version ^11.0|^12.0|^13.0
illuminate/support Version ^11.0|^12.0|^13.0
symfony/finder Version ^7.0|^8.0
vlucas/phpdotenv Version ^5.4