list-repo-tasks
List mise tasks grouped by namespace with dependency info. TRIGGERS - mise tasks, task list, show tasks, available tasks.
Best use case
list-repo-tasks is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
List mise tasks grouped by namespace with dependency info. TRIGGERS - mise tasks, task list, show tasks, available tasks.
Teams using list-repo-tasks should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/list-repo-tasks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How list-repo-tasks Compares
| Feature / Agent | list-repo-tasks | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
List mise tasks grouped by namespace with dependency info. TRIGGERS - mise tasks, task list, show tasks, available tasks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /mise:list-repo-tasks
List all mise tasks in the current repo, grouped by namespace with dependency information.
> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
## Step 1: Get Task List
```bash
mise tasks ls 2>/dev/null
```
If no tasks found, report:
```
No mise tasks found in this repo.
To create release tasks: /mise:run-full-release
To learn task authoring: See mise-tasks skill
```
## Step 2: Group by Namespace
Parse the task list and group by colon-prefix namespace:
- `release:*` — Release workflow tasks
- `test:*` — Testing tasks
- `cache:*` — Cache management tasks
- `dev:*` — Development quality tasks (fmt, lint, typecheck)
- `validate:*` — Validation tasks
- `smoke:*` — Smoke/integration tests
- `bench:*` — Benchmarking
- Tasks without a namespace prefix go under "General"
## Step 3: Filter by Argument
If a namespace argument is provided (e.g., `/mise:list-repo-tasks release`):
- Filter to only tasks matching that namespace prefix
- Show the dependency DAG for those tasks:
```bash
# Show task details including depends
mise tasks ls --json 2>/dev/null | jq '.[] | select(.name | startswith("release:"))'
```
## Step 4: Show Dependency Chains
For filtered namespaces, show the dependency chain:
```
release:full
└─ depends: release:postflight, release:pypi
└─ release:postflight depends: smoke, release:build-all
└─ release:build-all depends: release:version
└─ release:version depends: release:sync
└─ release:sync depends: release:preflight
```
## Example Output
```
═══════════════════════════════════════════
mise Tasks: rangebar-py (45 tasks)
═══════════════════════════════════════════
release (10 tasks):
full Full release: version → build → smoke → publish
dry Preview without changes
status Current version info
preflight Validate prerequisites
version Bump version via semantic-release
build-all Build all platform artifacts
macos-arm64 Build macOS ARM64 wheel
linux Build Linux wheel (cross-compile)
sdist Build source distribution
pypi Publish to PyPI
dev (4 tasks):
fmt Format code (cargo fmt + ruff)
lint Lint code (clippy + ruff)
test Run test suite
deny Check dependencies (cargo-deny)
cache (3 tasks):
status Show cache population status
populate Populate ClickHouse cache
clear Clear local cache
General:
smoke Integration smoke tests
bench Benchmarking suite
═══════════════════════════════════════════
```
## Post-Execution Reflection
After this skill completes, reflect before closing the task:
0. **Locate yourself.** — Find this SKILL.md's canonical path before editing.
1. **What failed?** — Fix the instruction that caused it.
2. **What worked better than expected?** — Promote to recommended practice.
3. **What drifted?** — Fix any script, reference, or dependency that no longer matches reality.
4. **Log it.** — Evolution-log entry with trigger, fix, and evidence.
Do NOT defer. The next invocation inherits whatever you leave behind.Related Skills
list-dialogs
Use when user wants to list all Telegram chats, groups, and channels, see their contacts, find a chat ID, browse conversations, or check account info via whoami.
mise-tasks
Orchestrate multi-step project workflows using mise task definitions with dependency management and argument handling. Use whenever the user wants to create, edit, or debug mise tasks, wire up task dependencies with depends/depends_post, or run workflows via 'mise run'. Also use when setting up task runners or automating build pipelines through mise. Do NOT use for mise environment variable configuration (use mise-configuration instead) or for general shell scripting unrelated to mise.
bootstrap-monorepo
Autonomous polyglot monorepo bootstrap meta-prompt. TRIGGERS - new monorepo, polyglot setup, scaffold Python+Rust+Bun, monorepo from scratch.
voice-quality-audition
Audition Kokoro TTS voices to compare quality and grade. TRIGGERS - audition voices, kokoro voices, voice comparison, tts voice, voice quality, compare voices.
settings-and-tuning
Configure TTS voices, speed, timeouts, queue depth, and bot settings. TRIGGERS - configure tts, change voice, tts speed, queue depth, tts timeout, bot config, tune settings, adjust parameters.
full-stack-bootstrap
One-time bootstrap for Kokoro TTS engine, Telegram bot, and BotFather setup. TRIGGERS - setup tts, install kokoro, botfather, bootstrap tts-tg-sync, configure telegram bot, full stack setup.
diagnostic-issue-resolver
Diagnose and resolve TTS and Telegram bot issues. TRIGGERS - tts not working, bot not responding, kokoro error, audio not playing, lock stuck, telegram bot troubleshoot, diagnose issue.
component-version-upgrade
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro, clean tts, teardown, component removal.
send-message
Use when user wants to send a text message on Telegram as their personal account via MTProto, text someone, or message a contact by username, phone, or chat ID.
send-media
Use when user wants to send or upload a file, photo, video, voice note, or document on Telegram via their personal account.
search-messages
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.