Get a repo ready with an agent
Hand your agent a prompt that gets an existing repository ready to deploy, and stops before it pushes.
All pages
- Run the agent in the root of the repository, with a clean working tree, so the diff it makes is only its own.
- The code is on GitHub. Connecting it through the Ghaym GitHub App is a step you take yourself, as Deploy from GitHub shows; an agent can't finish it alone.
- The prompts only read and edit files in the repository. None of them calls Ghaym, so the agent needs no key.
- Each prompt is checked against what these pages document, not measured, so there's no success rate. Read the diff before you push.
The prompt expects a package.json at the repository root. It checks the build and start scripts, audits the variables the repository reads and flags any secret behind NEXT_PUBLIC_, and lists the variables to set, split into server-only and public. Then it shows you the diff and stops.
Prepare this Next.js repository for deployment to Ghaym Cloud (a platform-as-a-service).
Context you must respect:
- Ghaym builds a container image from this repo. Ghaym auto-detects Node projects from package.json, so no Dockerfile is needed unless this repo has an unusual build.
- The app must listen on the port given in the PORT environment variable. `next start` already does this — do not hard-code a port in the start script.
- Secrets are set as environment variables in the Ghaym console. Do not commit them and do not invent values.
- Any variable prefixed NEXT_PUBLIC_ is inlined into the browser bundle and is public. Never put a secret behind that prefix.
- The `ghaym` CLI is the main way to drive Ghaym Cloud (`npm i -g @ghaymjo/cli`): `ghaym cloud projects create --name <name>` and `ghaym cloud services create --project <project> --type git --repo <owner/name> --size <size> --site <slug>` set the project up — and after that, every deploy is a git push to the production branch, because Ghaym builds what it pulls from the connected repository.
Tasks:
1. Check package.json: confirm `build` and `start` scripts exist and that `start` does not hard-code a port. Fix if needed.
2. Audit every environment variable this repo reads. Flag any NEXT_PUBLIC_ variable that looks like a secret.
3. List every environment variable I must set in the Ghaym console, split into server-only and public, with a one-line description each. Do not fill in values.
4. Do not push. Show me the diff and stop.The prompt expects a composer.json at the repository root. It adds a Dockerfile that starts the app on all addresses, on the port in PORT, and a .dockerignore that keeps .env and vendor out. It lists the variables to set, then shows you the diff and stops.
Prepare this Laravel repository for deployment to Ghaym Cloud (a platform-as-a-service).
Context you must respect:
- Ghaym builds a container image from this repo. Most languages are detected on their own; anything else needs a Dockerfile. This repo builds from one, so it needs a Dockerfile. A repository that already has a Dockerfile when its service is added builds from it.
- The app must listen on 0.0.0.0 and on the port given in the PORT environment variable. Do not hard-code a port.
- Secrets (APP_KEY, database credentials) are set as environment variables in the Ghaym console. Do not commit them, and do not invent values.
- The `ghaym` CLI is the main way to drive Ghaym Cloud (`npm i -g @ghaymjo/cli`): `ghaym cloud projects create --name <name>` and `ghaym cloud services create --project <project> --type git --repo <owner/name> --size <size> --site <slug>` set the project up — and after that, every deploy is a git push to the production branch, because Ghaym builds what it pulls from the connected repository.
Tasks:
1. Add a production Dockerfile that installs PHP extensions Laravel needs (including pdo_pgsql), runs `composer install --no-dev`, and starts the app bound to 0.0.0.0:$PORT.
2. Add a .dockerignore that excludes .env, vendor, node_modules, and storage caches.
3. List every environment variable I must set in the Ghaym console, with a one-line description each. Do not fill in values.
4. Do not push. Show me the diff and stop.Once you've read the diff, push it, and give the agent the rest of the work.