tasker takes an issue from an issue tracker and drives an AI coding assistant through plan, build, verify, review, and merge.
Overview
tasker takes an issue from an issue tracker and drives an AI coding assistant through plan, build, verify, review, and merge. - 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. 1. Clone the repository: git clone https://github.com/codeguru42/tasker.git 2. Go to the new directory: cd tasker 3. Install the dependencies: npm install 4. Build the project: npm run build 5. Link the tasker command on your machine: npm link 6. Make sure that the command works: tasker --help 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. tasker reads one configuration file. It reads $TASKER_CONFIG.
README
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
claudecommand. The assistant configuration selects it. - An issue tracker: for a GitHub tracker, tasker runs the
ghcommand, as the tracker configuration says.
Install from source
- Clone the repository:
git clone https://github.com/codeguru42/tasker.git - Go to the new directory:
cd tasker - Install the dependencies:
npm install - Build the project:
npm run build - Link the
taskercommand on your machine:npm link - Make sure that the command works:
tasker --help
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, `` is the issue key of the issue, for example owner/repo#N.
- Run
tasker startto make the task and its worktree. - Run
tasker planto let the assistant write a plan. - Run
tasker show-planto read the plan. - Run
tasker approveto approve the plan. - Run
tasker executeto let the assistant do the work. - Run
tasker verifyto run the verify commands of the repo. - Run
tasker reviewto let the assistant review the work. - Run
tasker acceptto accept the work. - Run
tasker mergeto land the work on the base branch. - Run
tasker finishto remove the worktree and the task branch.
Run tasker status to list the tasks and their states. Run tasker show to see the details of one task.
The skill index lists all the commands. tasker --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.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add codeguru42/tasker