task · diff
git:20261011.50a302f to git:20261018.db6acdb
3 added, 3 removed. Audit C to C.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
\<task_skill_guides>
You are executing a task within the LobeHub task system. Use the `lh task` CLI via `runCommand` to manage your task and related resources.
# Task Lifecycle
| Command | Description |
| ------------------------------- | ----------------------------------------------------- |
- | `lh task view <id>` | View task details, instruction, workspace, activities |
+ | `lh task view <id>` | View task details, instruction, documents, activities |
| `lh task edit <id>` | Update task name, instruction, status, priority |
| `lh task complete <id>` | Mark task as completed |
| `lh task comment <id> -m "..."` | Add a progress comment |
| `lh task tree <id>` | View subtask tree with dependencies |
# Working with Subtasks
| Command | Description |
| ----------------------------------------- | ----------------- |
| `lh task create -i "..." --parent <id>` | Create a subtask |
| `lh task list --parent <id>` | List subtasks |
| `lh task sort <parentId> <id1> <id2> ...` | Reorder subtasks |
| `lh task dep add <id> <dependsOnId>` | Add dependency |
| `lh task dep rm <id> <dependsOnId>` | Remove dependency |
- # Task Workspace (Documents)
+ # Task Documents
| Command | Description |
| ------------------------------------------------- | ------------------------- |
| `lh task doc create <id> -t "title" -b "content"` | Create and pin a document |
| `lh task doc pin <id> <docId>` | Pin existing document |
| `lh task doc unpin <id> <docId>` | Unpin document |
# Task Topics (Conversations)
| Command | Description |
| ----------------------------------- | ------------------------ |
| `lh task topic list <id>` | List conversation topics |
| `lh task topic view <id> <topicId>` | View topic messages |
# Usage Pattern
1. Read the reference file for detailed command options: `readReference('references/commands')`
2. Run commands via `runCommand` — the `lh` prefix is automatically handled
3. Use `--json` flag on any command for structured output
4. Use `lh task <subcommand> --help` for full command-line help
# Task Execution Guidelines
- **Check your task first**: Use `lh task view` to understand the full instruction and context
- - **Use workspace documents**: Store outputs and deliverables as task documents
+ - **Use task documents**: Store outputs and deliverables as task documents
- **Report progress**: Use `lh task comment` to log key milestones
- **Respect dependencies**: Check `lh task tree` to understand task ordering
- **Complete when done**: Use `lh task complete` when all deliverables are ready
- **Automation tasks are the exception — NEVER complete them**: a task with automation (heartbeat or schedule — shown as an `Automation:` line in the task context) is a recurring loop, and this run is one tick of it. NEVER run `lh task complete` (or set a terminal status via `lh task edit --status`) on that task: a terminal status permanently disarms the loop — no future tick will fire and nothing recovers it. A tick with nothing to do, or whose condition is not met yet, is still a successful run; just finish your turn and the next tick is armed automatically. Only the user retires a recurring task.
- **End conditions**: the one exception is when the instruction itself defines when the loop ends ("until X", "stop once Y", "after Z is merged") and this tick has verified it is now met. Then run `lh task complete <id>` as your final step: it is finalized after this run finishes and retires the loop. Do not ask the user to stop it instead — nobody reads a tick's reply in real time.
\</task_skill_guides>