← ClaudeAtlas

jjtasklisted

Structured TODO commit workflow using JJ (Jujutsu). Use when user mentions jjtask, jj task, task IDs to work on, revisions with [task:*] flags, or wants to manage tasks. Plan tasks as empty commits with [task:*] flags, track progress through status transitions, manage parallel task DAGs. Enforces completion discipline.
Divyxnk44x/jjtask · ★ 0 · AI & Automation · score 72
Install: claude install-skill Divyxnk44x/jjtask
<context> Designed for JJ 0.36.x+. Uses revset aliases and templates defined in jjtask config. </context> <objective> Manage a DAG of empty revisions as TODO markers representing tasks. Revision descriptions act as specifications. Two roles: Planners (create empty revisions with specs) and Workers (implement them). For JJ basics (revsets, commands, recovery), see the `/jj` skill. </objective> <quick_start> ```bash # 1. Plan: Create TODO tasks jjtask create "Add user validation" "Check email format and password strength" jjtask create --chain "Add validation tests" "Test valid/invalid emails and passwords" # 2. Start working on a task jjtask wip abc123 # Single task: @ becomes the task (jj edit) # Multiple WIP: @ becomes merge commit # 3. Work and complete # For single task: work directly in @ # For merge: jj edit TASK to work in specific task jjtask done abc123 # Task rebases ON TOP of work commits, then @ rebases onto task # 4. Flatten for push jjtask squash # Squashes all merged task content into linear commit ``` </quick_start> <workflow_trigger> When user references a task ID and expects work to begin (e.g., "work on lu", "do task xy", "here's the task spec"): 1. Run `jjtask wip <id>` FIRST before any investigation 2. Then read spec, investigate, implement 3. Run `jjtask done` only when all criteria met </workflow_trigger> <commands> | Command | Purpose | | -------------------------------------- | -------