name

vsc-taskrunner-skill

description

Configure and use runtask for everyday development, middleware containers, VS Code task execution, and Web UI-driven CI/CD workflows. Use when creating or editing .vscode/tasks.json or runtask-ui.yaml, generating language and container tasks, replacing Docker Compose with lightweight local tasks, adding TCP or HTTP readiness checks, configuring branches, auth, schedules, artifacts, storage, or runtime modes, and answering runtask CLI questions.

VSC Taskrunner

Configure and operate runtask across local development and Web UI-driven automation. Prefer direct, reviewable edits to .vscode/tasks.json and runtask-ui.yaml; use interactive generators when they provide the intended task scaffold.

Workflow

Inspect README.md, .vscode/tasks.json, runtask-ui.yaml, and the repository's language/tool files.
Identify the requested surface and read the matching reference:
- Task execution, generators, UI commands, and readiness commands: references/command-reference.md
- Compose-equivalent, low-memory local development: references/compose-development.md
- Web UI configuration and CI/CD-style execution: references/ui-configuration.md
Edit only the source files needed for the request. Preserve unrelated configuration and user changes.
Read and apply references/validation-checklist.md before finishing.
Report changed files, validation performed, and any assumptions that remain.

Editing Rules

Keep the runtask-ui.yaml schema comment on the first line.
Treat .vscode/tasks.json as the shared task definition for VS Code, local CLI execution, development orchestration, and Web UI runs.
Use exact task labels from .vscode/tasks.json; treat task and branch patterns as first-match-wins policies.
Select UI runtime mode with runtask ui --runtime-mode=always-on|serverless, not with a YAML field.
Keep secrets out of committed files. Use environment-variable placeholders in examples.
Prefer mise for installing project languages and tools.
Keep a Compose migration small: add container tasks, add build or application tasks, add readiness tasks, then add one aggregate dev task.
Use waitlisten for TCP ports or HTTP(S) URLs. Add --label when the target name is clearer than its address.
Do not expose every task in the Web UI by default. Add only tasks intended for CI/CD-style, remote, or browser-triggered execution.

Choosing References

Read only the material needed for the current change, but always use the validation checklist.

For ordinary CLI use, task generation, or command syntax, read command-reference.md first.
For container startup, application dependencies, waitlisten, or an aggregate dev task, read compose-development.md.
For a new or changed Web UI or CI/CD-style setup, read ui-configuration.md.
For review-only requests, inspect the relevant reference and apply validation-checklist.md without mutating files.

Expected Result

Produce the requested configuration or documentation with:

valid, minimal YAML or JSON;
cross-platform container behavior where the generator supports it;
explicit dependency ordering and readiness checks;
no embedded credentials;
a concise validation summary.

VSC Taskrunner

Workflow

Inspect README.md, .vscode/tasks.json, runtask-ui.yaml, and the repository's language/tool files.

Identify the requested surface and read the matching reference:

Task execution, generators, UI commands, and readiness commands: references/command-reference.md
Compose-equivalent, low-memory local development: references/compose-development.md
Web UI configuration and CI/CD-style execution: references/ui-configuration.md

Edit only the source files needed for the request. Preserve unrelated configuration and user changes.

Read and apply references/validation-checklist.md before finishing.

Report changed files, validation performed, and any assumptions that remain.

Editing Rules

Keep the runtask-ui.yaml schema comment on the first line.

Treat .vscode/tasks.json as the shared task definition for VS Code, local CLI execution, development orchestration, and Web UI runs.

Use exact task labels from .vscode/tasks.json; treat task and branch patterns as first-match-wins policies.

Select UI runtime mode with runtask ui --runtime-mode=always-on|serverless, not with a YAML field.

Keep secrets out of committed files. Use environment-variable placeholders in examples.

Prefer mise for installing project languages and tools.

Keep a Compose migration small: add container tasks, add build or application tasks, add readiness tasks, then add one aggregate dev task.

Use waitlisten for TCP ports or HTTP(S) URLs. Add --label when the target name is clearer than its address.

Do not expose every task in the Web UI by default. Add only tasks intended for CI/CD-style, remote, or browser-triggered execution.

Choosing References

Read only the material needed for the current change, but always use the validation checklist.

For ordinary CLI use, task generation, or command syntax, read command-reference.md first.

For container startup, application dependencies, waitlisten, or an aggregate dev task, read compose-development.md.

For a new or changed Web UI or CI/CD-style setup, read ui-configuration.md.

For review-only requests, inspect the relevant reference and apply validation-checklist.md without mutating files.

Expected Result

Produce the requested configuration or documentation with:

valid, minimal YAML or JSON;

cross-platform container behavior where the generator supports it;

explicit dependency ordering and readiness checks;

no embedded credentials;

a concise validation summary.