delete-content

To safely delete content, you can scan for cross-references and validate permissions via RULE.md to prevent broken links. This skill checks dependencies and requires explicit confirmation before proceeding with deletion or archiving.

Archiving outdated notes instead of permanently deleting them is handled by reading governance rules from RULE.md to determine archiving options. It automatically updates parent READMEs and preserves references while removing the active content.

Checking if a file has cross-references before removing it from a repository is performed by scanning for dependency links to prevent orphaned references. The operation pauses for explicit user confirmation after validating these dependencies.

You can enforce governance rules for content deletion using a RULE.md file by configuring it to determine whether deletions are allowed. The skill reads this file to validate permissions and decide whether to delete, archive, or back up content.

You do not need to update parent READMEs manually after pruning files from a knowledge base. The skill automatically updates parent READMEs and archive references as needed during the governance-compliant deletion process.