Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
joaquimscosta avatar

Taskfile Setup

  • 1 installs
  • 21 repo stars
  • Updated August 5, 2026
  • joaquimscosta/arkhe-claude-plugins

Installs Taskfile and scaffolds or audits Taskfile.yml with ecosystem-aware templates for Node, JVM/Gradle, Python/uv, and Docker.

About

Installs the Task runner and scaffolds or audits Taskfile.yml using ecosystem-aware templates, auto-detecting Node, JVM, Python, and Docker. A developer uses it to add or standardize developer task automation in a project.

  • Auto-detects ecosystems for template selection
  • Recommends single-file vs multi-file includes patterns

Taskfile Setup by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,173 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/joaquimscosta/arkhe-claude-plugins --skill taskfile-setup

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars21
Last updatedAugust 5, 2026
Repositoryjoaquimscosta/arkhe-claude-plugins

What it does

Installs Taskfile and scaffolds or audits Taskfile.yml with ecosystem-aware templates for Node, JVM/Gradle, Python/uv, and Docker.

Files

SKILL.mdMarkdownGitHub ↗

Taskfile Setup

Install Taskfile and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates.

Pre-flight

Run the detection script to understand current state:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_taskfile.py <project-root>

Decision Flow

Run detector
    |
    ├── task_binary.installed = false → Install Task first
    |
    ├── taskfile.exists = true → Phase 1: Audit
    |
    └── taskfile.exists = false → Phase 2: Scaffold

Phase 1: Audit (Existing Taskfile)

1. Summarize findings — show a status table:

ComponentStatusDetail
task binaryinstalled/missingversion, path
Taskfilefound/not foundpath, variant
TasksN taskscount, has includes
EcosystemsN detectedlist
dotenvconfigured/missing.env files found

2. Present audit violations grouped by severity (ERROR > WARNING > INFO):

  • Show rule ID, message, task name, line number, fix hint
  • Violations include: missing version, no preconditions on deploy tasks, no sources/generates on build tasks, missing desc, too many tasks in single file, no dotenv, hard-coded paths

3. Use `AskUserQuestion` (multiSelect: true) — ask which violations to fix

4. Apply selected fixes — see WORKFLOW.md for per-rule fix strategies

5. Re-run detector to verify fixes were applied

Phase 2: Scaffold (No Taskfile)

1. Install `task` if missing — show commands based on os field:

  • macOS: brew install go-task
  • Linux: sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
  • Verify: task --version

2. Review detected ecosystems — show what was found

3. Choose Taskfile pattern — use AskUserQuestion:

  • Single-file (flat namespace with : separators) — recommended for < 15 tasks
  • Multi-file (root + taskfiles/ with includes) — recommended for 15+ tasks or monorepos

4. Choose task groups — use AskUserQuestion (multiSelect: true):

EcosystemAvailable Groups
Node.js/pnpmdev, build, test, lint, format, check
JVM/Gradlebuild, test, lint, check, run
Python/uvdev, test, lint, format, check
Dockerup, down, logs, build, clean
Genericsetup, check, clean

5. Generate Taskfile.yml with selected groups — always include:

  • version: "3"
  • desc: on every task
  • Top-level vars: for directory paths
  • dotenv: if .env files exist

6. Verify — re-run detector, then run task --list

Key Rules

  • Never overwrite existing Taskfile.yml without asking. Offer merge/replace/skip.
  • Detect first — skip steps already configured.
  • Use `AskUserQuestion` for every decision. Do not assume user preferences.
  • Always use `version: "3"` — the only supported non-deprecated schema.
  • Add `desc:` to every task for task --list discoverability.
  • Wrap ecosystem tools (pnpm, gradlew, uv) — do not duplicate their logic.
  • Use variables for directory paths instead of hard-coding.
  • dotenv only in root — Taskfile does not support dotenv in included files.

Existing Runner Awareness

The detector reports existing runners (Makefile, justfile, package.json scripts, gradlew). When scaffolding:

  • Note which runners exist and what they cover
  • Suggest Taskfile as a unifying layer that wraps existing tools
  • Do not duplicate what existing runners already do well

References

  • Workflow: See WORKFLOW.md for detailed per-step flows and templates
  • Examples: See EXAMPLES.md for example setup and audit sessions
  • Troubleshooting: See TROUBLESHOOTING.md for common issues
  • Detection Script: See scripts/detect_taskfile.py for detection logic

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.