
List Repo Tasks
- 85 installs
- 62 repo stars
- Updated August 3, 2026
- terrylica/cc-skills
Helps with ai & agent building tasks.
About
list-repo-tasks is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- list-repo-tasks
- AI & Agent Building
- AI-coding skill
List Repo Tasks by the numbers
- 85 all-time installs (skills.sh)
- Ranked #5,069 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/terrylica/cc-skills --skill list-repo-tasksAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 85 |
|---|---|
| repo stars | ★ 62 |
| Last updated | August 3, 2026 |
| Repository | terrylica/cc-skills ↗ |
What it does
Helps with ai & agent building tasks.
Files
/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/nullIf 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 skillStep 2: Group by Namespace
Parse the task list and group by colon-prefix namespace:
release:*— Release workflow taskstest:*— Testing taskscache:*— Cache management tasksdev:*— Development quality tasks (fmt, lint, typecheck)validate:*— Validation taskssmoke:*— Smoke/integration testsbench:*— 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:preflightExample 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.
Evolution Log
Convention: Reverse chronological order (newest on top, oldest at bottom). Prepend new entries.
---
2026-02-26: Initial Evolution Log
Status: Skill is in use and maintained. Track improvements here.
Purpose
This evolution log tracks updates to the skill. Each entry should note:
- What changed (content, structure, tooling)
- Why it changed (bug fix, feature request, best practice)
- Files affected
How to Use
1. When updating SKILL.md or references, add an entry here with the date 2. Keep entries reverse-chronological (newest first) 3. Link to ADRs or GitHub issues when relevant 4. Reference specific line changes when helpful
---