update-branch

Update NovaDB branch attributes by id with a values array.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/novadb/claude-plugins --skill update-branch-novadb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-branch
Source: https://github.com/novadb/claude-plugins/tree/main/consulting/skills/update-branch
Command: npx skills add https://github.com/novadb/claude-plugins --skill update-branch-novadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update-branch provides a concise, auditable way to change attributes of an existing NovaDB branch without creating a new branch or performing manual API wiring, reducing mistakes and preserving history.

Core Features & Use Cases

  • Targeted attribute updates: Change name, parent, branch type, workflow state, due date, or assignee by specifying only the fields you want to modify.
  • Partial updates and audit support: Values are supplied as CmsValue objects so omitted fields remain unchanged and optional comment and username fields capture an audit trail.
  • Use Case: Reassign a branch to a different user and update its name and due date during a sprint re-planning operation.

Quick Start

Update branch 2100500 to change its name to Updated Name and assign it to newuser by calling the update-branch skill with id 2100500 and a values array specifying the name and assignee attributes.

Frequently Asked Questions about update-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update NovaDB branch attributes like assignee or due date without creating a new branch?

To update NovaDB branch attributes, submit an existing branch id and a values array of CmsValue objects to modify fields like name, parent, type, state, due date, or assignee. Omitted fields remain unchanged, preserving original data.

Can I perform a partial branch property update in NovaDB?

Yes, partial branch property updates are supported by supplying only the specific CmsValue objects you want to modify. Fields not included in the values array remain completely unchanged during the transaction.

How do I track who changed a branch state or assignee in NovaDB?

You can track branch changes by passing optional comment and username parameters when updating branch attributes. This captures an auditable trail of who made the change and why, returning transaction details.

What is the best way to reassign a NovaDB branch to a different user during sprint re-planning?

The best way to reassign a NovaDB branch is to call the update function with the branch id and a CmsValue array specifying the new assignee. You can also simultaneously update the name and due date.

Does updating a NovaDB branch return transaction details for integration scripts?

Yes, updating a NovaDB branch returns the updatedObjects count and specific transaction details. This allows scripts and integrations to verify that targeted attribute changes were applied successfully.

What NovaDB branch fields can be modified using a targeted attribute update?

You can modify the name, parent, branch type, workflow state, due date, and assignee fields of an existing NovaDB branch. These properties are changed by submitting a corresponding CmsValue array.