Project workflow commands. Use when user says: pdev, pinstall, psave, ppush, ppr, pmerge — or dev, install, save, push, pr, merge as standalone messages.
Common project workflow actions. Each command is goal-oriented — it describes the desired end state, not the exact steps. The agent figures out how to get there.
| Command | Shortcut | What it does |
|---|---|---|
| dev | pdev | Get the dev server running |
| install | pinstall | Build the project and install it as a production artifact |
| save | psave | Quick checkpoint — commit everything, no verification |
| push | ppush | Full lockdown — verify, commit everything, push |
| pr | ppr | Create or show a pull request |
| pmerge |
| Merge one or all pull requests from GitHub |
Match the user's input to a command file. The user may use the full name, the p-prefixed shortcut, or a synonym — all route to the same command.
| Input | Command file |
|---|---|
dev, pdev | commands/dev.md |
install, pinstall, build, ship | commands/install.md |
save, psave | commands/save.md |
push, ppush | commands/push.md |
pr, ppr | commands/pr.md |
merge, pmerge, merge <number>, pmerge <number>, merge all, pmerge all | commands/merge.md |
These commands represent desired outcomes, not prescriptive recipes:
If something can't be done (no git repo, no dev script found), say so clearly. If something is optional and missing (no remote upstream), just skip it silently.