GitKraken Cli Documentation

How to Manage Work Items in GitKraken CLI

Last updated: October 2026

Deprecated: As of GitKraken CLI 3.1.76, the gk work and gk workspace commands are deprecated and will be removed in a future release. They still work, but each command prints a deprecation warning. There’s no direct replacement. For single-repository work, use standard Git commands with the GitKraken CLI AI features, such as gk ai commit and gk ai pr create.

A work item is a task, such as a bug fix or feature, that spans more than one repository in your GitKraken workspace. With gk work, you can start the task, review changes, commit, open pull requests, and clean up in every repository at once, instead of repeating each step in each repository.

Requirements

To use work items, you need the following:

  • Workspace: an active GitKraken workspace that contains the repositories you’re working in.
  • Plan: you can use work items on any plan. AI-assisted actions require a paid plan.
  • Account: sign in with gk auth login to use GitKraken cloud features.
  • Organization: set an organization with gk organization set <ORG_NAME> to generate commits and pull requests with AI.
  • Scope: every gk work command runs in every repository in the active workspace.

The following table summarizes the work item commands:

Command Use it to Needs AI or sign-in Result
gk work start <name> Start a task across multiple repositories No Creates the work item across the workspace
gk work info Review pending changes before you commit or open pull requests No Shows the work item’s state in each repository
gk work commit --ai Commit in each repository with AI-generated messages Yes, and a paid plan Commits staged changes in each affected repository
gk work pr create --ai Open pull requests for the work item Yes, and a paid plan Creates pull requests for every repository with changes
gk work end Finish the work item and clean up No Closes the work item and offers cleanup options

For every option, see the gk work command reference.


When to Use GitKraken CLI Work Items Instead of Standard Git Commands

Use gk work when one issue, bug fix, or feature spans multiple repositories in the same workspace. If your work stays in one repository and you don’t need matching commits, pull requests, or cleanup across repositories, use standard Git commands instead.


How to Start a GitKraken CLI Work Item Quickly

Follow these steps for the shortest path through a multi-repository task. The next section explains each command in detail.

  1. Start a new work item:
    gk work start <name>
  2. Review pending changes in every repository in the workspace:
    gk work info
  3. Stage your changes with git add, then commit with an AI-generated message:
    gk work commit --ai
  4. Create pull requests for every repository in the work item:
    gk work pr create --ai
  5. Finish and clean up the work item:
    gk work end

Every gk work command runs in parallel in every repository in the active workspace. To generate commit messages and pull requests with AI, you need to be signed in, have an organization set, and have a paid plan.


How to Run a GitKraken CLI Work Item from Start to Finish

To create a task that spans every repository in the active workspace, run gk work start:

gk work start <name>

The <name> is the title of your work item. GitKraken CLI sets up each repository in your workspace and checks for pending commits, pull requests, or open work items.

Terminal output of gk work start setting up each repository in the workspace and checking for pending items.
Starting a work item sets up your workspace and checks for pending items.

Before you commit or open pull requests, review the state of the work item with gk work info:

gk work info
Terminal output of gk work info listing the changes in each repository of the work item.
Use gk work info to review changes in every repository.

How to Commit Work Item Changes with AI

To generate commit messages and commit your staged changes in each repository of the work item, run:

gk work commit --ai

This command does the following:

  • Analyzes your staged changes with AI.
  • Writes a commit message that fits each change.
  • Commits the changes in each repository in the work item.

To choose the AI model for one run, add --model <MODEL_ID>. To learn more about models, see How to Use AI Features in GitKraken CLI.

Terminal output of gk work commit --ai showing AI-generated commit messages for each repository.
AI-generated commit messages help keep your commit history consistent.

How to Create Pull Requests for a Work Item with AI

To open pull requests for every repository in the active work item, run:

gk work pr create --ai

GitKraken CLI creates a pull request with an AI-generated title and description for each repository that has changes in the work item. Run this command after you review the work item and commit your changes.

How to End and Clean Up a Work Item

When the task is complete, close the work item and clean up its temporary resources:

gk work end

GitKraken CLI asks whether to delete or keep your local changes, then removes the work item’s temporary resources.

Have feedback about this article? Did we miss something? Let us know!
On this page