modifying-diva-entity

Modifies DIVA business entity tables across dictionary, screen mask, and SQL layers.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill modifying-diva-entity-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modifying-diva-entity
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/modifying-diva-entity
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill modifying-diva-entity-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Evolving an existing DIVA business table (adding, modifying, or removing a field) requires coordinated changes across the data dictionary (.dhsd), the screen mask (.dhsf), recompilation, and SQL synchronization, with byte-position recalculation that is error-prone when done manually. ## Core Features & Use Cases - Dictionary Field Operations: Add, modify, or remove fields in a .dhsd table with automatic position recalculation, Filler adjustment, and index position updates. - FK Zoom Binding: Attach a standard zoom (foreign key toward T013, T007, ART, CLI) to an existing field via Module Check (.dhsp) and mask updates. - Human-Validated Workflow: A 7-step orchestration with 4 validation checkpoints, optional SVN pre-modification checks, and automatic .bak backups. - Use Case: A developer needs to add a NbPages field (Nature 11,0) after Libelle in the Livre table; the skill lists current fields, presents the impact, applies the change with backup, validates the dictionary, updates the mask, recompiles, and syncs SQL. ## Quick Start Ask the assistant to add a new field with a given Nature to a specific table in your .dhsd dictionary and let it guide you through the validation checkpoints.

Frequently Asked Questions about modifying-diva-entity

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

FAQPage Schema
How do I add a field to a DIVA dictionary table?

Run modify_dhsd_table.py with --action add-field, providing --dhsd, --table, --name, --nature, and optionally --after and --backup. The script recalculates field positions, adjusts the Filler, creates the [CHAMP] declaration if needed, and updates the table Taille.

How do I change the Nature of an existing DIVA field?

Use modify_dhsd_table.py with --action modify-field, --name, and --new-nature. The script updates the [CHAMP] Nature declaration, recalculates positions and Filler, and recomputes cumulative positions for any index containing the field.

Can I delete a field from a DIVA table without losing data?

No. Removing a field followed by SQL synchronization drops the column and causes irreversible data loss, which the workflow explicitly warns about at checkpoint CP1. Standard fields, the U-field, and Filler are protected and cannot be removed.

Does the skill support adding a foreign key zoom to a field?

Yes, the add-fk operation binds a standard zoom (toward T013, T007, ART, CLI) to an existing field by updating the Module Check (.dhsp) and the mask (.dhsf) via the binding-zoom-to-field skill. It does not modify the dictionary, and the target field must already exist.

What happens if SVN is unavailable during the pre-modification check?

The check degrades gracefully: check_svn_recent.py returns svn_available=false and the workflow continues without SVN enrichment. All SVN access is read-only through a whitelist of subcommands like log, diff, and blame.