generate-run-commands

Generate and update session run commands in .vscode/tasks.json.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/aadorian/VSCode_Readme --skill generate-run-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-run-commands
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/sessions-chat-and-agents/sessions/skills/generate-run-commands
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill generate-run-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you add or update session run commands so the right setup and development tasks appear in the Agent Session Run button without manual task-file editing.

Core Features & Use Cases

  • Detect Existing Run Commands: Checks .vscode/tasks.json for tasks already marked to show in sessions.
  • Infer Common Project Commands: Looks at workspace files to suggest setup and launch commands such as install, build, or dev tasks.
  • Merge Safely: Updates the task file while preserving unrelated tasks and configuration.
  • Use Case: A team onboarding a new workspace can quickly surface dependency installation and local start commands in the session toolbar.

Quick Start

Ask the skill to inspect your workspace and add the appropriate session run command to .vscode/tasks.json.

Frequently Asked Questions about generate-run-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add setup and dev tasks to the VS Code Run button for Agent Sessions?

Session run commands are generated and updated in .vscode/tasks.json to surface setup and launch tasks in the Agent Session Run button. The skill detects existing inSession tasks and infers new ones from workspace files.

How do I automatically infer install and launch commands for my workspace tasks?

Workspace files are inspected to infer common project commands like install, build, or dev tasks. These inferred commands are then added to .vscode/tasks.json so they appear in the session toolbar.

Will updating tasks.json overwrite my existing VS Code tasks?

Updating tasks.json uses a safe merge behavior that preserves unrelated tasks and configuration. The skill detects tasks already marked for sessions and only modifies or adds the necessary run commands.

What is the best way to surface dependency installation and local start commands for team onboarding?

Surfacing dependency installation and local start commands is done by generating session run commands in .vscode/tasks.json. This allows new team members to quickly access setup and development workflows via the Run button.

Can I use this to set up run commands for first-run worktree setup?

First-run worktree setup is supported by generating session run commands in .vscode/tasks.json. The skill applies to projects needing initial workspace configuration and ongoing development workflows surfaced in the Run button.

Why are my setup and launch tasks not showing in the Sessions Run button?

Tasks may not be properly marked in .vscode/tasks.json to show in sessions. The skill detects existing inSession tasks and updates the file safely to ensure the correct setup and launch commands appear in the Run button.