rtk-ai / rtk-ai/rtk

Add PHP and laravel (artisan, sale) commands

Open
#2,245 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area:cli enhancement help wanted priority:medium
Dominant language
Rust
Stars
81.1k
Forks
5.1k
Avg merge
4d 21h
Merged PRs (30d)
35

Description

Context

Running rtk discover on my project revealed that 284 out of 675 unhandled commands are Laravel Sail variants — making it the single largest savings opportunity not yet covered by RTK.

Top unhandled commands
Command Count Example
sail artisan 148 vendor/bin/sail artisan test --testsuite=...
sail exec 82 vendor/bin/sail exec pgsql psql -U sail...
sail bin 54 vendor/bin/sail bin pint --dirty --format=...
sail composer 4 vendor/bin/sail composer require ...
What I'd expect

RTK wrappers similar to existing ones, e.g.:


rtk sail artisan <args>   →  vendor/bin/sail artisan <args>

rtk sail exec <args>      →  vendor/bin/sail exec <args>

rtk sail bin <args>       →  vendor/bin/sail bin <args>

rtk sail composer <args>  →  vendor/bin/sail composer <args>

Or alternatively — a generic rtk sail <subcommand> <args> that proxies all Sail subcommands.

Why it matters

Laravel Sail is the standard Docker-based dev environment for Laravel projects. These commands produce large tool_result outputs (test runners, psql sessions, code formatters), so RTK's token-saving behavior would be particularly valuable here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by locating the existing RTK command wrappers and the command-discovery or proxy entry point. Exercise the listed Sail commands, including artisan, exec, bin, and composer, and confirm that the chosen wrapper approach forwards arguments while providing RTK's output reduction; the issue leaves the specific-command versus generic-proxy design open.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, laravel, php
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.