Manage tasks via dex CLI. Use when breaking down complex work, tracking implementation items, or persisting context across sessions.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use dex directly for all commands. If not on PATH, use npx @zeeg/dex instead.
command -v dex &>/dev/null && echo "use: dex" || echo "use: npx @zeeg/dex"
Dex tasks are tickets - structured artifacts with comprehensive context:
Think: "Would someone understand the what, why, and how from this task alone?"
Never reference dex task IDs in external artifacts (commits, PRs, docs). Task IDs like abc123 become meaningless once tasks are completed. Describe the work itself, not the task that tracked it.
Use dex when:
Skip dex when:
Some AI agents (like Claude Code) have built-in task tools. These are session-only and not the same as dex.
| dex | Built-in Task Tools | |
|---|---|---|
| Persistence | Files in .dex/ | Session-only |
| Context | Rich (description + context + result) | Basic |
| Hierarchy | 3-level (epic → task → subtask) | Flat |
Use dex for persistent work. Use built-in task tools for ephemeral in-session tracking only.
dex create "Short name" --description "Full implementation context"
Description should include: what needs to be done, why, implementation approach, and acceptance criteria. See examples.md for good/bad examples.
dex list # Pending tasks
dex list --ready # Unblocked tasks
dex show <id> # Full details
dex complete <id> --result "What was accomplished" --commit <sha>
GitHub/Shortcut-linked tasks require either --commit <sha> or --no-commit:
--commit <sha> when you have code changes (issue closes when merged)--no-commit for non-code tasks like planning or design (issue stays open)Always verify before completing. Results must include evidence: test counts, build status, manual testing outcomes. See verification.md for the full checklist.
dex edit <id> --description "Updated description"
dex delete <id>
For full CLI reference including blockers, see cli-reference.md.
Tasks have two text fields:
dex list)--full)When you run dex show <id>, the description may be truncated. The CLI will hint at --full if there's more content.
When picking up a task, gather all relevant context:
dex show <id> --full # Full task details
dex show <parent-id> --full # Parent context (if applicable)
dex show <blocker-id> --full # What blockers accomplished
Before starting, verify you can answer:
If any answer is unclear:
Proceed without full context when:
Three levels: Epic (large initiative) → Task (significant work) → Subtask (atomic step).
Choosing the right level:
# Create subtask under parent
dex create --parent <id> "Subtask name" --description "..."
For detailed hierarchy guidance, see hierarchies.md.
Complete tasks immediately after implementing AND verifying:
Your result must include explicit verification evidence. Don't just describe what you did—prove it works. See verification.md.
When a task is linked to a GitHub issue (shown in dex show output), include issue references in commit messages:
Fixes #N
Refs #N
Check dex show <id> for GitHub issue info before committing. The "(via parent)" indicator means use Refs, direct metadata means use Fixes.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when adding release notes, changelog entries, user-facing changes, internal changelog notes, or preparing a PR/release for django-language-server. Handles Keep a Changelog formatting and entry style.
中文简介正在准备中。当前显示原文说明。
Use when editing Django template parser tags, validation errors, diagnostics, environment scanning, inspector data, Python environment inventory, or DJLS domain model code. Handles project-specific semantic and parser conventions.
中文简介正在准备中。当前显示原文说明。
Maintain the ported ty resolver test corpus in crates/djls-project/tests/resolve.rs. Use when bumping the ruff git pin in the workspace Cargo.toml or when adding/reviewing module-resolution tests.
中文简介正在准备中。当前显示原文说明。
Use when editing djls-extraction or Rust code that consumes Ruff Python AST APIs, including parse_module, parameters, boxed expressions, f-strings, or exception handlers. Handles known Ruff AST shape gotchas in django-language-server.
中文简介正在准备中。当前显示原文说明。
Use when editing Salsa inputs, tracked functions, database traits, setters, SemanticDb, crate::Db, invalidation behavior, or incremental computation in django-language-server. Handles project-specific Salsa conventions and required impl updates.
中文简介正在准备中。当前显示原文说明。
Use when running tests, fixing failing tests, updating snapshots, syncing corpus data, validating before push, or working with Django matrix testing in django-language-server. Handles cargo, just, nox, insta, corpus, clippy, fmt, and lint commands.
中文简介正在准备中。当前显示原文说明。