ratchet-uninstall

Removes Ratchet framework files from a GitHub repository via a manifest-driven uninstall script and PR.

2|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/praveenvijayan/Ratchet --skill ratchet-uninstall-praveenvijayan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet-uninstall
Source: https://github.com/praveenvijayan/Ratchet/tree/main/plugin/skills/ratchet-uninstall
Command: npx skills add https://github.com/praveenvijayan/Ratchet --skill ratchet-uninstall-praveenvijayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Removing an installed agent-delivery framework by hand risks deleting user-authored files or leaving orphaned GitHub state. This Skill performs a safe, manifest-driven teardown of Ratchet that only removes files recorded in .ratchet-install.json, preserves generated files and plans by default, and routes file removal through a pull request. ## Core Features & Use Cases - Manifest-driven removal: Reads .ratchet-install.json to decide exactly what to delete, refusing to remove anything not recorded there, and keeps any framework file whose content hash shows local modifications. - Dry-run preview: Runs scripts/ratchet-uninstall.sh without flags first to show the user exactly which framework, generated, and plan files would be affected before any deletion. - PR-based file removal: Performs deletions on a ratchet-uninstall branch and opens a PR, since main is protected. - Opt-in GitHub cleanup: Offers per-item confirmation to delete state:*/priority:* labels, the FACTORY_PAT secret, the RATCHET_AUTO variable, planning branches, and open planning PRs — while never deleting issues or branch protection. - Use Case: A team decides to stop using the Ratchet delivery loop. The agent previews the teardown, removes framework files via a reviewed PR, keeps GATES.md and memory/, and cleans up labels and secrets only after explicit approval. ## Quick Start Ask the agent to uninstall Ratchet from this repository, previewing what will be removed first and keeping my generated files and plans.

Frequently Asked Questions about ratchet-uninstall

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

FAQPage Schema
How do I uninstall Ratchet from my GitHub repository?

Run the uninstall flow, which first previews removals via `scripts/ratchet-uninstall.sh` in dry-run mode, then deletes framework files on a `ratchet-uninstall` branch and opens a PR. Merge the PR to complete file removal, then confirm any GitHub-side cleanup items individually.

How do I remove a framework without deleting my own project files?

Use a manifest-driven uninstaller that only removes paths recorded in `.ratchet-install.json`. Generated files like `GATES.md` and `memory/`, plus `plan/*.md`, are kept by default, and locally modified framework files are preserved based on content-hash comparison.

What happens if .ratchet-install.json is missing during uninstall?

The uninstall script exits immediately with a clear message and removes nothing, since the manifest is the only source of truth for what belongs to Ratchet. You must either reinstall with `scripts/bootstrap.sh` to generate a manifest or remove files manually.

Does uninstalling Ratchet delete my GitHub issues or branch protection?

No. Issues are never deleted because they are user work items, and branch protection is never removed since it is a user safety setting. Optional cleanup covers only labels, the FACTORY_PAT secret, the RATCHET_AUTO variable, and planning branches, each requiring explicit confirmation.

Why does the uninstall fail when pushing directly to main?

The main branch is normally protected, so direct pushes are rejected. The workflow instead creates a `ratchet-uninstall` branch, commits the removals there, and opens a pull request for review and merge.