$ loading_
Generate or update session run commands for faster project startup and testing.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "generate-run-commands" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode/main/src/vs/sessions/skills/generate-run-commands/SKILL.md 2. Save it as ~/.claude/skills/generate-run-commands/SKILL.md 3. Reload skills and tell me it's ready
Generate a run command for the current Node.js project so the Run button starts the development server, preferably using scripts from package.json.
Returns a suitable startup command, such as npm run dev, and can apply it to the session run configuration.
Modify the current run command so it activates the virtual environment before starting the app. The entry point is app.py. Provide a command suitable for the Run button.
Returns an updated Python run command that includes virtual environment activation and app startup.
This repository has both frontend and backend services. Generate run commands for the Run button that start both services, using existing scripts whenever possible.
Returns a combined run setup for the full-stack project, describing the commands or scripts used and updating the current session configuration.
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.
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){
"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
}
]
}
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:
package.json, Makefile, pyproject.toml, Cargo.toml, go.mod, .nvmrc, or other project files to understand the stack and common commands.npm install, pip install -r requirements.txt), add it with "runOptions": { "runOn": "worktreeCreated" } — no need to ask.npm run dev, cargo run), add it with just "inAgents": true.Always write to .vscode/tasks.json in the workspace root. If the file already exists, merge — do not overwrite unrelated tasks.
After writing, briefly confirm what was added and how to trigger it from the Run button.
Validate Azure DevOps pipeline changes and troubleshoot builds and YAML faster.
Update the GitHub Copilot CLI or SDK to a newer version.
Upgrade Anthropic SDKs, migrate versions, and fix dependency or typing issues.
Generate or update chat customization files for AI coding agents.
Find and read Code OSS dev build logs for faster debugging.
Merge session branch changes back into the base branch cleanly.
Create a pull request from the current session's code changes.
Diagnose misconfigurations, failures, and unexpected behavior in the current Amplifier session.
Create a draft pull request from the current session’s code changes.
Create commits for code changes with AI-generated messages matching repo style.
Process submitted session feedback and turn it into targeted improvements.
Plan actionable option proposals for runbook examples.