← ClaudeAtlas

generate-run-commandslisted

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Pointa-Labs/basehalf · ★ 15 · AI & Automation · score 73
Install: claude install-skill Pointa-Labs/basehalf
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. --> # Generate Run Commands Help the user set up run commands for the current Agent Session workspace. Run commands appear in the session's Run button in the title bar. ## Understanding the task schema A run command is a `tasks.json` task with: - `"inAgents": true` — required: makes the task appear in the Agents run button - `"runOptions": { "runOn": "worktreeCreated" }` — optional: auto-runs the task whenever a new worktree is created (use for setup/install commands) ```json { "tasks": [ { "label": "Install dependencies", "type": "shell", "command": "npm install", "inAgents": true, "runOptions": { "runOn": "worktreeCreated" } }, { "label": "Start dev server", "type": "shell", "command": "npm run dev", "inAgents": true } ] } ``` ## Decision logic **First, read the existing `.vscode/tasks.json`** to check for existing run commands (`inAgents: true` tasks). **If run commands already exist:** treat this as a modify request — ask the user what they'd like to change (add, remove, or update a command). **If no run commands exist:** try to infer the right commands from the workspace: - Check `package.json`, `Makefile`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `.nvmrc`, or other project files to understand the stack and common commands. - If it's clear what the setup command is (e.g.,