Skill v1.0.1
currentAutomated scan100/1003 files
version: "1.0.1" name: delete-doc description: Delete documentation pages interactively with confirmation.
Instructions
When user wants to delete documentation:
Step 1: Understand What to Delete
Ask the user:
"What would you like to delete?
- A specific page - Tell me which page(s)
- Find unused pages - I'll identify orphan pages not in navigation
- Deprecated content - I'll find pages marked as deprecated
- Clean up - Describe what you want removed"
Step 2: Identify Pages
Based on their choice:
For Specific Page:
- "Which page(s)? (e.g.,
guides/old-feature.mdx)" - Verify the file exists
- Check for incoming links from other pages
For Unused Pages:
Scan for orphan pages:
Compare:- All .mdx files in docs/- Pages referenced in docs.jsonOrphan pages (not in navigation):- docs/drafts/unused.mdx- docs/old/deprecated-guide.mdx
For Deprecated Content:
Search for deprecation markers:
Files with deprecation notices:- docs/api/legacy-auth.mdx (marked deprecated in v1.5)- docs/guides/old-workflow.mdx (marked deprecated in v2.0)
Step 3: Analyze Impact
Before deletion, check for:
- Incoming links - Other pages linking to this page
- Navigation - Entry in docs.json
- Redirects - Should we redirect to a new page?
Show analysis:
"Deletion Analysis for `guides/old-feature.mdx`:
Incoming links (2 pages reference this):
quickstart.mdx:45→ links to/guides/old-featureapi/overview.mdx:23→ links to/guides/old-feature#setup
Navigation:
- Listed in docs.json under 'Guides' group
Recommended actions:
- Remove from docs.json
- Update or remove links in other pages
- Consider redirect to replacement page"
Step 4: Confirm Deletion
"Ready to delete guides/old-feature.mdx?
This will:
- ❌ Delete the file
- ❌ Remove from docs.json navigation
- ⚠️ Leave broken links in 2 pages (I can fix these)
Options:
- Delete and fix links - Remove file, update linking pages
- Delete and redirect - Remove file, add redirect to
{new-page} - Delete only - Just remove the file
- Cancel - Don't delete"
Step 5: Execute Deletion
Based on user choice:
Delete and Fix Links:
- Delete the MDX file
- Update docs.json (remove page entry)
- Find and update/remove links in other pages:
```mdx // Before See the old feature guide.
// After See the new feature guide. // or remove the sentence entirely ```
Delete and Redirect:
- Delete the MDX file
- Update docs.json
- Add redirect to docs.json or redirects file:
``json { "redirects": [ { "from": "/guides/old-feature", "to": "/guides/new-feature" } ] } ``
Delete Only:
- Delete the MDX file
- Update docs.json
- Warn about broken links
Step 6: Summary
"Deleted:
- ❌
docs/guides/old-feature.mdx - ✓ Removed from docs.json navigation
- ✓ Updated links in
quickstart.mdx,api/overview.mdx - ✓ Added redirect:
/guides/old-feature→/guides/new-feature
Want me to commit these changes? Use /commit when ready."
Bulk Deletion
For multiple pages:
"Found 5 orphan pages not in navigation:
| File | Last Modified | Size | |
|---|---|---|---|
drafts/test.mdx | 6 months ago | 2kb | |
old/legacy-api.mdx | 1 year ago | 15kb | |
temp/scratch.mdx | 3 months ago | 1kb | |
guides/draft-feature.mdx | 2 months ago | 8kb | |
archive/v1-docs.mdx | 1 year ago | 20kb |
Options:
- Delete all - Remove all orphan pages
- Select pages - Choose which to delete
- Review each - Go through one by one
- Cancel - Keep all pages"
Safety Guidelines
- Always confirm before deleting
- Check for links to prevent broken references
- Offer redirects for removed public pages
- Show impact before executing
- Keep backup by suggesting to commit before deletion
- Never delete docs.json or context.json without explicit confirmation