tasker

tasker takes an issue from an issue tracker and drives an AI coding assistant through plan, build, verify, review, and merge.

Requirements

• Node.js 26 or later
• npm
• git
• An AI coding assistant: tasker runs Claude Code with the claude command. The assistant configuration selects it.
• An issue tracker: for a GitHub tracker, tasker runs the gh command, as the tracker configuration says. The gh login of the account of issueTracker.account needs the token scope repo, as the token scopes say.

Install

1. Clone the repository: git clone https://github.com/codeguru42/tasker.git. In an existing clone, run git fetch --tags instead.
2. Go to the folder of the clone: cd tasker
3. Check out the tag of the version: git checkout v<version>
4. Install the dependencies: npm ci
5. Make the package file: npm pack
6. Install the package file: npm install -g ./tasker-<version>.tgz
7. Make sure that tasker --version prints <version>.
8. Run tasker install-skills, so that an assistant finds the tasker skill.

For an update, do the same steps with the tag of the new version.

tasker --help lists the options and the commands. tasker --version prints the version. tasker with no command prints the same usage to stderr and exits with code 1. An unknown command or option prints an error and exits with a non-zero code.

Configuration

tasker reads one configuration file. It reads $TASKER_CONFIG. If that is not set, it reads $XDG_CONFIG_HOME/tasker/config.json. If that is not set, it reads $HOME/.config/tasker/config.json.

See the configuration reference for the keys. Run tasker show-config to see the configuration with the defaults filled in. Run tasker doctor to make sure that the machine is set up.

Quick start

In each command, <issue> is the issue key of the issue, for example owner/repo#N.

1. Run tasker start <issue> to make the task and its worktree.
2. Run tasker plan <issue> to let the assistant write a plan.
3. Run tasker show-plan <issue> to read the plan.
4. Run tasker approve <issue> to approve the plan.
5. Run tasker execute <issue> to let the assistant do the work.
6. Run tasker verify <issue> to run the verify commands of the repo.
7. Run tasker review <issue> to let the assistant review the work.
8. Run tasker accept <issue> to accept the work.
9. Run tasker merge <issue> to land the work on the base branch.
10. Run tasker finish <issue> to remove the worktree and the task branch.

Run tasker status to list the tasks and their states. Run tasker show <issue> to see the details of one task.

The skill index lists all the commands. tasker <command> --help gives the options of a command.

States

Each task moves through states. A command works only in some states. The state machine doc gives the states and the edges.

Contributing

See CONTRIBUTING.md to start work as a contributor.