bknd-delete-entity

Delete BKND database entities with dependency checks and backups.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cameronapak/melos --skill bknd-delete-entity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bknd-delete-entity
Source: https://github.com/cameronapak/melos/tree/main/.agents/skills/bknd-delete-entity
Command: npx skills add https://github.com/cameronapak/melos --skill bknd-delete-entity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bknd.

What problem does it solve?

This Skill guides users through safely removing a BKND database entity, addressing dependencies, protecting data, and synchronizing schema changes. The workflow emphasizes backups, relationship cleanup, and careful execution to prevent accidental data loss.

Core Features & Use Cases

  • Dependency-aware deletion: Removes an entity only after examining and resolving related records and foreign keys.
  • Backup-first workflow: Prompts and demonstrates how to back up data before deletion to enable recovery.
  • Schema and sync guidance: Walks through removing relations from the schema and running a dry-run before destructive operations.
  • Batch/dependent deletions: Provides a pattern for deleting multiple entities in correct order to maintain referential integrity.

Quick Start

  1. Review all dependencies and backup the database.
  2. Run a dry-run sync to preview changes (no destructive actions).
  3. Apply the deletion with the --drop flag and validate that the entity is removed.

Frequently Asked Questions about bknd-delete-entity

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

FAQPage Schema
How do I safely delete a database entity with foreign key dependencies?

To safely delete a database entity with dependencies, you must examine related records and foreign keys, update schema references, and run a dry-run preview before applying destructive changes to maintain referential integrity.

What's the best way to remove a BKND schema entity without losing data?

The best way to remove a BKND schema entity without data loss is following a backup-first workflow: create a data backup, run a dry-run sync to preview changes, then apply the deletion with the --drop flag and validate the removal.

Do I need to back up my database before removing an entity in a production environment?

Yes, you need to back up your database before removing an entity in production. A backup-first workflow prompts you to create recovery data before executing destructive operations, ensuring you can restore data if needed.

How does a dry-run sync work when deleting database entities?

A dry-run sync previews entity deletion changes without executing destructive actions. It allows you to validate that schema references are updated and relationships are cleaned up before actually applying the removal with the --drop flag.

Can I delete multiple database entities that have relationships with each other?

Yes, you can delete multiple dependent database entities by following a specific pattern that removes them in the correct order. This batch deletion approach maintains referential integrity by resolving foreign keys and related records sequentially.

Why does deleting an entity break referential integrity in my schema?

Deleting an entity breaks referential integrity when related records and foreign keys are not resolved first. To prevent this, you must remove relations from the schema and clean up dependent data before applying the deletion.