delete-doc

Delete documentation pages with confirmation prompts and backlink checks.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/brainfish-ai/devdoc --skill delete-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delete-doc
Source: https://github.com/brainfish-ai/devdoc/tree/main/public-apis/meta/.claude/skills/delete-doc
Command: npx skills add https://github.com/brainfish-ai/devdoc --skill delete-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delete decisions in documentation workflows should not be made without safeguards to prevent accidental removal. This Skill helps teams prevent accidental deletions by enforcing an explicit confirmation workflow when removing documentation pages.

Core Features & Use Cases

  • Interactive confirmation prompts before deletion.
  • Identifies navigation references and incoming links to assess impact before removal.
  • Suggests safe redirects or navigation updates to preserve user experience.

Quick Start

Remove a page with confirmation: Remove docs/guides/old-feature.mdx and confirm when prompted.

Frequently Asked Questions about delete-doc

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

FAQPage Schema
How do I safely delete documentation pages without breaking navigation links?

Deleting deprecated documentation content interactively prompts for explicit confirmation before removing selected pages. The workflow checks navigation references and proposes redirects to safe replacement pages.

What happens to backlinks when I remove a page from my docs repository?

Removing a page from a docs repository triggers a check for backlinks and navigation entries. Safe redirects or navigation updates are then proposed to preserve user experience.

Can I remove multiple selected documentation pages at the same time?

Yes, the interactive workflow applies to removing multiple selected pages or deprecated content across the docs repository. Explicit confirmation prompts are enforced to prevent accidental deletion.

What is the best way to remove deprecated content from docs navigation references?

Using an interactive confirmation workflow to remove deprecated content from docs navigation references ensures safety. It checks backlinks, assesses impact, and proposes redirects to replacement pages.

Why do I need explicit confirmation to delete a single documentation page?

Explicit confirmation prevents accidental removal by enforcing safeguards on delete decisions in documentation workflows. This ensures user experience is preserved before any page is removed.