jig-task | You describe work to do, ask to continue something, ask what to take next, or ask to set priorities | Finds an existing task or classifies the new one by risk (T0–T4), creates its workspace and branch when the work needs them (small work that fits one session needs neither), names the route and starts the first stage. At session start, lists merged tasks waiting to be closed. Asked what next, it takes the answer of jig queue next instead of choosing. Gives a task it files a priority, and asked to set priorities it writes them to the queue. | Which task, when several are live on the branch; whether each merged task can be closed. |
jig-autopilot | You hand a task over to be done without you (Autopilot) | Runs the task’s whole route without waiting between stages, limits fixing to two attempts, and ends with the change handed over and a report. Given a phase of a roadmap instead of a task, it coordinates a wave of tasks built in parallel (running a whole phase). | Only at a stop: a design approval, a problem it could not fix, a decision nobody made, or a destructive step. |
jig-setup | After jig init, or whenever you want to change what your agent may do on its own | Asks you, one question at a time and with a recommendation, how far the agent may take a finished task, whether it may merge and whether autopilot may run without asking; shows the whole .ai/config.local.yaml it would write (personal settings). When origin has a stage or staging branch, it also asks the team’s git flow and, after a yes, puts it in .ai/config.yaml through a task of its own. | Each setting, one at a time; your yes before anything is written — and an explicit yes for merging and for running without questions. |
jig-idea | An idea that is not settled yet, work too big for one task, or a new project’s architecture and stack | Talks before it writes. Works in circles of a few rounds: the first round brings ideas of its own next to yours, the later ones stress what is on the table. Each circle ends with what it would write down and where else the idea could go. Keeps the conversation in a draft git never sees, so a session cut short loses nothing. Writes the specification with a roadmap in .ai/specs/ only after you say so, and ships it once. Starts no task and changes no code. Files a phase’s tasks when asked. | Each round’s questions together, numbered, each with its recommendation; then whether to write it down or go another circle. |
jig-release | You want the next release planned and made | Lists the live tasks with their goals, proposes which go in and in what order, and whether the version rises by a patch or a minor; once you agree, orders them in the queue, and when they have merged writes the release notes checked against the diffs as the last pull request — the one that raises the version — and ships it as far as your settings allow. | The list and the version level, before anything is created. |
jig-pr-review | You give the link of a colleague’s GitHub pull request or GitLab merge request to review — in any folder: the installer places this skill for you as well as in each project | Fetches it into a detached worktree of your clone without touching your checkout, reviews it with jig-review’s method against the rules of its base, runs nothing from it, checks every serious finding a second time, places the comments on the forge’s own diff, marks each finding with its severity and numbers it (a ranked review has not yet been checked on a live pull or merge request), shows the review word for word as it would be posted, and after your yes to that version posts it — on GitHub as one comment-only review, on GitLab as one discussion per comment (each one notifies the author) — as the account that may comment, and reads back where each comment landed. A multi-line comment on GitLab is posted at its last line, and the review shown says so; posting to GitLab has not yet been checked on a live merge request. After the author pushes fixes, a follow-up reads that review back from the forge, finds the head it read even after a force-push (or says it is gone), judges each earlier thread against the new code, comments only on what changed, and answers each thread “fixed” or “still open” in the same gate; the follow-up has not yet been checked on a live pull or merge request. | Which account to post as, when none or several may comment; the comments’ language, when the pull request’s thread is in another one; your yes to the review as shown. |
jig-upgrade | You want a project’s Jig brought up to date, or jig status says it is behind | Updates the tool when a newer release is out, runs jig upgrade with a dry run first, and lists the steps the release asks for by hand — doing those it can. The upgrade is shipped as far as your settings allow (Upgrading). | Before resolving anything that would stop the upgrade: your uncommitted changes, a task’s branch checked out, the team’s .gitattributes. |