add-form-field

Append an attribute definition to a NovaDB form field list.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Appends a single attribute definition to a form's field list without replacing other fields, preventing manual errors and incorrect ordering when updating multi-value CmsValue entries.

Core Features & Use Cases

  • Safe Append: Reads existing attribute 5053 values and appends a new attribute definition while preserving all other fields.
  • Deterministic Ordering: Rebuilds all 5053 CmsValue entries with incrementing sortReverse values so the new field is appended at the end.
  • Integration Use Case: Automate adding a new field to an existing NovaDB form (typeRef 50) during schema updates, branch workflows, or UI-driven form edits.

Quick Start

Use the add-form-field skill to append a new attribute definition ID to form <formId> on branch <branch> by reading existing 5053 values and sending the rebuilt values back.

Frequently Asked Questions about add-form-field

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

FAQPage Schema
How do I add a new field to a NovaDB form without overwriting existing fields?

To safely append a field to a NovaDB form, read existing attribute 5053 values first. Rebuild all CmsValue entries with incrementing sortReverse values so the new field is appended at the end, then send the complete replacement back via novadb_cms_update_objects.

What is the correct sortReverse ordering when updating NovaDB form field lists?

Correct sortReverse ordering requires rebuilding all 5053 CmsValue entries with incrementing sortReverse values. This deterministic ordering ensures the newly appended attribute definition is placed at the end of the form's field list during the novadb_cms_update_objects replacement.

Why does updating a NovaDB form attribute replace all existing fields?

Updating a NovaDB form attribute replaces all existing fields because novadb_cms_update_objects expects a complete replacement of the 5053 CmsValue multi-value entries. To prevent data loss, you must read and reconstruct all current field definitions before appending the new attribute.

Can I append multiple attribute definitions to a NovaDB form at once?

No, this process is designed to append a single new field to a form's field list without replacing other fields. It targets typeRef 50 objects and handles one attribute definition at a time to ensure correct read-modify-write ordering and prevent manual errors.

When do I need to use novadb_cms_get_object for form schema updates?

You need to use novadb_cms_get_object for form schema updates when performing a read-modify-write operation to append a field. It retrieves the existing 5053 attribute values from the typeRef 50 form object so you can reconstruct the full field list before updating.