mcpField
L
list-repo-tasks

list-repo-tasks

github.com/terrylicaDevelopment288 installsUpdated today
Repository

About list-repo-tasks

list-repo-tasks is a skill for listing mise tasks in the current repository, aimed at developers who need to understand task groups and dependencies. It can filter by namespace and show dependency chains for matching tasks.

Key features

  1. 01Lists mise tasks in a repository
  2. 02Groups tasks by namespace
  3. 03Filters tasks by namespace argument
  4. 04Shows dependency chains for filtered tasks

Use cases

  1. 01Inventorying repository automation tasks
  2. 02Inspecting release-task dependencies
  3. 03Filtering test or validation tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/terrylica/cc-skills --skill list-repo-tasks

After installing, type/list-repo-tasksin Claude Code to confirm it loaded.

Bundled filesreferences/evolution-log.md

Details

From the project README

/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

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:
# 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:

  1. Locate yourself. — Find this SKILL.md's canonical path before editing.
  2. What failed? — Fix the instruction that caused it.
  3. What worked better than expected? — Promote to recommended practice.
  4. What drifted? — Fix any script, reference, or dependency that no longer matches reality.
  5. Log it. — Evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.

Comments

Markdown supported