blog-delete

Deletes a selected BeeKite or removes it from the system.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/carter2099/.dotfiles-homelab --skill blog-delete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-delete
Source: https://github.com/carter2099/.dotfiles-homelab/tree/main/.claude/skills/blog-delete
Command: npx skills add https://github.com/carter2099/.dotfiles-homelab --skill blog-delete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables safe removal of blog content by soft-deleting the markdown post file (moving it to a deleted/ directory) and permanently destroying the corresponding database record, ensuring recoverability of the file while removing the live data.

Core Features & Use Cases

  • Soft-delete the post or review by moving its markdown file to a deleted/ folder and marking it as removed from active listings.
  • Permanently delete the database record to remove the content from the site and backups.
  • Support identification by ID or title, with candidate listing and explicit confirmation before action.

Quick Start

Identify the target by ID or title, confirm the deletion, and trigger the soft-delete of the markdown file with permanent DB removal.

Frequently Asked Questions about blog-delete

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

FAQPage Schema
How do I safely delete a blog post in Rails while keeping the markdown file recoverable?

To safely delete a blog post in Rails, this Skill performs a soft-delete by moving the markdown file to a deleted/ directory while permanently destroying the corresponding database record, ensuring the content file remains recoverable. It requires explicit confirmation before executing the destructive action.

What is the difference between soft-deleting a markdown file and permanently destroying a database record?

Soft-deleting a markdown file moves the content to a deleted/ directory for recoverability, while permanently destroying the database record removes the live data from the active site listings and backups. This approach ensures the file is preserved without remaining accessible on the live application.

Can I identify a Rails blog post for deletion by title instead of ID?

Yes, you can identify a Rails blog post for deletion by either ID or title. When using a title, the Skill lists candidate posts matching the query and requires explicit confirmation before proceeding with the soft-delete of the markdown file and the permanent removal of the database record.

Does soft-deleting a Rails blog post remove it from the live site and database backups?

Yes, soft-deleting removes the post from the live site and database backups by permanently destroying the database record. The associated markdown file is moved to a deleted/ directory, meaning the text content is preserved locally but is no longer present in the active database or its backups.

How to verify a blog post database record is permanently deleted in Rails?

To verify a blog post database record is permanently deleted in Rails, the Skill performs a verification check ensuring the record no longer exists in the database after the destructive action. This confirms the permanent removal was successful alongside the markdown file soft-delete.

When should I not use a soft-delete approach for removing blog posts?

You should not use a soft-delete approach if you need to completely erase the markdown file content without leaving a recoverable copy in the deleted/ directory. This Skill is designed for safe removal, meaning the markdown file is intentionally preserved even though the database record is permanently destroyed.