debug-task

Diagnose and fix broken, misconfigured, or misbehaving moon tasks.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/notwillk/rulesy --skill debug-task-notwillk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-task
Source: https://github.com/notwillk/rulesy/tree/main/.agents/skills/debug-task
Command: npx skills add https://github.com/notwillk/rulesy --skill debug-task-notwillk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moon tasks can fail, skip, hang, or produce stale cache results for many non-obvious reasons, and this Skill provides a structured five-step diagnostic flow to isolate the root cause quickly instead of guessing. ## Core Features & Use Cases - Resolved Config Inspection: Uses moon task <project>:<task> --json to verify command vs script usage, inputs, outputs, deps, checks, tags, and inheritance merge results. - Cache Diagnosis: Compares hash manifests with moon hash to pinpoint stale cache hits, unexpected cache misses, and outputs that fail to restore after hydration. - Symptom-to-Cause Mapping: A lookup table routes symptoms like "nothing to do", pipeline hangs, mutex contention, and runInCI surprises to the correct reference guide. - Use Case: A developer's build task re-runs on every CI run despite unchanged sources; the Skill walks them through hash diffing to discover a volatile fingerprint check output invalidating the cache. ## Quick Start Ask the assistant to debug why your moon task is failing or misbehaving, providing the specific project:task target to inspect.

Frequently Asked Questions about debug-task

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

FAQPage Schema
How do I debug a moon task that is failing?

Start by inspecting the resolved configuration with `moon task <project>:<task> --json`, then run with `moon run <target> --log debug --force` to see toolchain resolution, hash generation, and process execution details.

Why does my moon task re-run every time instead of using cache?

Cache misses happen when inputs are too broad, outputs contain volatile files like timestamps, or a fingerprint check produces changing output. Diff two consecutive runs with `moon hash <hash1> <hash2>` to find the changing field.

Why is my moon task skipped or showing nothing to do?

Common causes include the --affected flag with no changed inputs, runInCI settings like 'only' or 'skip', an os platform filter, or all condition checks passing in v2.4. Check options in `moon task <target> --json`.

What moon version is required for task checks and cacheStrategy?

Dependency cacheStrategy and task tags require moon v2.3 or later, while task checks (requirement, condition, fingerprint) and project-level taskOptions require v2.4. The skill overall requires moon v2.0 minimum.

Why does my moon pipeline hang or deadlock?

A persistent task listed in another task's deps causes a hard error in moon v2, and shared mutex values can serialize or deadlock tasks. Visualize the dependency chain with `moon action-graph <target>` to find the blocking node.

When should I not use this debugging skill?

This skill only diagnoses existing tasks; it does not cover creating new tasks, setting up workspaces, configuring toolchains, or learning moon concepts. Use moon's official documentation for those scenarios.