workflow-taskfile
Use when running installs, dev servers, tests, lint/format, codegen, or Docker lifecycle tasks; Taskfile is the source of truth.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Workflow: Taskfile-first
When to use
- You need to install, run dev servers, lint/format, test, build, run codegen, or manage Docker lifecycle.
- You are unsure whether a workflow task exists.
Steps
- Inspect
Taskfile.yml(and included Taskfiles) to confirm valid targets. - If the workflow likely lives in a subdirectory, check for a local Taskfile
and use
task -d <dir> <target>. - If you cannot confirm a target, ask for
task --listortask --list-alloutput. - Prefer
task <target>over raw commands for workflows. - For unfamiliar tasks, use
task --summary <task>before execution.
Constraints and guardrails
- Do not invent task targets.
- Use raw commands only for read-only diagnostics unless you are also proposing a Taskfile wrapper.
- Do not recommend destructive operations (DB reset/drop, prune,
--force, volume deletion) without explicit confirmation. - If a required workflow is missing, add a Taskfile target and update README “Quick start / Dev tasks.”
References
-
Taskfile.yml -
backend/Taskfile.yml -
frontend/Taskfile.yml
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!