skills.rest
vickysrawat
vickysrawatCOMMUNITY
Explore all skills by this author →
GitHub

setup-teardown

Removes plugin-managed skills, hooks, rules, and state files from a project after dry-run confirmation.

1|Updated Jun 27, 2026
Search Tags:#devops#claude code#cleanup#plugin management#dry-run#teardown#configuration reset
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill setup-teardown-vickysrawat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-teardown
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/setup-teardown
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill setup-teardown-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It safely removes plugin-managed content from a project when you need to resolve deployment conflicts, reset after a major plugin version change, recover from configuration drift, or fully exit the plugin workflow — without ever touching developer-owned files like memory/. ## Core Features & Use Cases - Scoped Removal: Remove everything (--full) or target specific scopes: --skills, --hooks, --rules, --commands, or --state. - Dry-Run First: Always shows exactly what will be removed and requires an explicit CONFIRM before touching the filesystem. - Protected Content: Never removes memory/, CLAUDE.md (only strips plugin-managed sections), business-context.md, or customized pre-commit hooks. - Use Case: After upgrading the plugin and hitting conflicts from old .claude/skills/ deployments, run the teardown with --skills to cleanly remove stale skill files, then redeploy with /setup-sync. ## Quick Start Ask the assistant to run /setup-teardown with the --skills scope to preview and remove deployed plugin skills from this project.

Frequently Asked Questions about setup-teardown

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

FAQPage Schema
How do I remove plugin-managed files from my project?▼

Run /setup-teardown with a scope flag such as --full, --skills, --hooks, --rules, --commands, or --state. The skill always performs a dry-run first showing exactly what will be removed, then requires you to type CONFIRM before any filesystem change.

What is the difference between setup-teardown scopes?▼

--full removes all plugin-managed content, while --skills, --hooks, --rules, --commands, and --state each target one area only. After a scoped teardown, run /setup-sync to redeploy that area, or /setup-init after --full.

Does setup-teardown delete my memory folder or CLAUDE.md?▼

No. memory/ is never removed because it is developer-owned, and CLAUDE.md is never deleted entirely — only plugin-managed sections are stripped. Customized pre-commit hooks and business-context.md are also protected.

Why does teardown ask for confirmation before removing files?▼

The mandatory dry-run plus CONFIRM step prevents silent destruction of project configuration. The confirmation is case-insensitive, and any other input cancels the operation with nothing removed.

When should I use setup-teardown instead of setup-sync?▼

Use setup-teardown when setup-sync cannot fix accumulated drift incrementally, when resolving conflicts from pre-.hashes skill deployments, or when fully exiting the plugin workflow. For routine redeployment, setup-sync alone is sufficient.

Related Skills

Explore More Software Engineering Skills→
reggiechan74reggiechan74
5

plugins

Create, deploy, and govern Claude Code plugins with manifest and marketplace metadata.

Community
Intermediate
datamonsterrdatamonsterr

uv

Automate Python project management and environment setup with uv commands.

Community
Intermediate
agentctxagentctx
1

agentctx_skill

Deploy Claude Code skills to cloud storage with versioning and drift detection.

Official
Intermediate
methodic-researchmethodic-research
1

chronicle-mint-git-token

Mints a one-hour git access token and clone URL for a Chronicle experiment repository.

Official
Basic