Guide safe deletion of NetBox models across code, docs, UI, and API layers.
npx skills add https://github.com/netbox-community/netbox --skill remove-model
Please help me install this Agent Skill. Skill: remove-model Source: https://github.com/netbox-community/netbox/tree/main/.claude/skills/remove-model Command: npx skills add https://github.com/netbox-community/netbox --skill remove-model
Removing a NetBox model cleanly is risky because many parts of the system (UI, APIs, GraphQL, tests, docs, navigation, and database migrations) may reference it, causing import or runtime failures.
Use the remove-model guide when you need to deprecate or delete an existing NetBox model after confirming nothing retained has non-nullable foreign keys pointing to it.
High-intent search queries and answers about installing and using this skill.
To safely remove a NetBox model, delete all consumers first—tests, docs, navigation, GraphQL, REST, URLs, views, tables, forms, and filtersets—before removing the model itself to prevent import or runtime failures.
The correct workflow for model removal migration is generating Django migrations via makemigrations, including any RemoveField operations for foreign keys, and reviewing the migration file before applying it to the database.
You should not delete a NetBox model if retained models have non-nullable foreign keys pointing to it without addressing those dependencies first, as this will cause migration failures and broken references.
The best way to clean up API and GraphQL references during model removal is to systematically delete all consumers including GraphQL types, REST endpoints, URLs, views, and choices before removing the model class itself.
NetBox crashes on startup after model deletion because broken references remain in UI, APIs, GraphQL, tests, navigation, or database migrations that still import the removed model, requiring consumer-first removal.
ewe-studiosProvide reusable Django base classes for UUIDs, timestamps, and soft deletes.
Harigithub11Generates Django database migrations from model changes using the makemigrations workflow.
netbox-communityRemove NetBox model fields across API, UI, GraphQL, tests, and migrations.
mymx2Plan deprecation and migration of legacy systems with zero active usage verification.
