Create your account

Use case · By risk

Keep the reason for a branch change with the review

For maintainers reviewing changes to shared Git branches.

A force push or branch deletion can affect work other people still depend on. A short command does not explain the consequences. Describe the proposed branch change in a Work task, assign its owner and link the pull request. Add the review decision to the task discussion.

Create your accountWatch Security run →

Protected branches

Review the release branch cleanup

Example content

  1. Next action

    Confirm that no active work depends on the branch

  2. Context

    Target branch and reason for the change

  3. Evidence

    Pull request or comparison link

What to put in the task

  • Assign the task to the person responsible for the next action.
  • Add evidence links and explain what they show in a comment.
  • Update the task when the work changes so the next reader has the current state.

Before you rely on it

Command interception depends on your client's hooks or proxy; see the setup guide for Claude Code, Codex, Cursor and other MCP clients.

  • Specify tasks do not enforce Git branch protection. Configure protected branches and required reviews on your Git host.
  • Work must be enabled for the selected account, and you need permission to read or change the task. Security access and device setup are separate.

Related use cases and clients

By riskProduction changesThe person reviewing the release can read the proposed change and its supporting evidence in the same task.By riskDestructive operationsThe cleanup has a named owner and a written scope that a reviewer can check.By clientCodexSetup requirements for Codex.
All use cases →