Skill

create-snapshot

Use when the user wants to take a BTRFS snapshot before a risky change.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin snap-it

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Take a manual BTRFS snapshot before upgrades, config edits, or package installs.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars1

Forks0

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create Snapshot

Take a manual BTRFS snapshot before upgrades, config edits, or package installs.

When to use

Before running a risky system change

Creating a baseline before testing

Archiving a known-good state

Inputs to gather

Snapper config name (e.g., root, home)

Description (what change prompted this snapshot)

Snapshot type (optional; single default, or pre for paired pre/post)

Procedure

Preflight: Verify target is BTRFS. Confirm snapper is installed; fall back to raw btrfs subvolume snapshot if no config exists.

If snapper config exists: Run sudo snapper -c <config> create --type <type> --print-number -d "<description>". Capture the numeric ID.

If no snapper config: Run sudo btrfs subvolume snapshot <source> <dest> with a timestamped name.

Print the new snapshot ID to stdout (for caller to capture).

Output / side effects

New snapshot created on the target subvolume. Returns the snapshot ID.

Safety / constraints

Creates a read-only BTRFS snapshot. Requires sudo. No data modification; snapshot space depends on CoW changes afterward.

Create Snapshot

Take a manual BTRFS snapshot before upgrades, config edits, or package installs.

When to use

Before running a risky system change
Creating a baseline before testing
Archiving a known-good state

Inputs to gather

Snapper config name (e.g., root, home)
Description (what change prompted this snapshot)
Snapshot type (optional; single default, or pre for paired pre/post)

Procedure

Preflight: Verify target is BTRFS. Confirm snapper is installed; fall back to raw btrfs subvolume snapshot if no config exists.
If snapper config exists: Run sudo snapper -c <config> create --type <type> --print-number -d "<description>". Capture the numeric ID.
If no snapper config: Run sudo btrfs subvolume snapshot <source> <dest> with a timestamped name.
Print the new snapshot ID to stdout (for caller to capture).

Output / side effects

New snapshot created on the target subvolume. Returns the snapshot ID.

Safety / constraints

Creates a read-only BTRFS snapshot. Requires sudo. No data modification; snapshot space depends on CoW changes afterward.