taskfile-skills

Use when the user wants to author Taskfile content: creating new Taskfiles, adding new tasks, writing task dependencies/preconditions/variables, or restructuring tasks across files. The user might say "add a [name] task", "set up tasks for", "create a Taskfile", "where should this task go", "convert my Makefile", or simply describe task names and commands they want automated - even without saying "Taskfile" explicitly. Covers all ecosystems (cargo, yarn, wasm-pack, dotnet, cmake) and all scenarios: single projects, monorepos with nested includes, gitignored local overrides vs. shared dist files. Skip for: explaining how existing tasks work, debugging task run failures, or general go-task concept questions.

Taskfile discovery and execution — use before running any project command when the project may use go-task. Invoke when the user asks: "run the tests", "build the project", "start the dev server", "run lint/fmt/bench/ci/clean", "what task should I run for X", "task [name] is failing", "how do I pass args to task", or when a Taskfile.yaml/Taskfile.dist.yaml is present. Always read the Taskfile before guessing ecosystem commands — prevents npm-vs-yarn mistakes, wrong test wrappers (cargo test vs nextest), and missed env vars or dep chains. Covers task field inspection, nested includes, CLI_ARGS passthrough, and manual fallback when task is unavailable. Use taskfile-authoring when creating or updating Taskfiles.