signalproof-rollback

Selects and verifies trustworthy rollback targets from backups, versions, commits, and snapshots.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-rollback-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-rollback
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-rollback
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-rollback-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a system fails, teams often grab the newest backup or a folder named 'golden' without proving it can actually be restored, leading to failed recoveries and lost data. This Skill enforces evidence-based selection of a known-good rollback target before any restore begins. ## Core Features & Use Cases - Candidate Classification: Sorts backups, versions, commits, packages, snapshots, and installers into VERIFIED ROLLBACK, PROMISING CANDIDATE, BACKUP ONLY, REJECTED/FAILED, or UNKNOWN classes. - Identity and Integrity Verification: Records version/build/commit identity and checks hashes, manifests, signatures, and runtime/dependency/schema compatibility. - STOP Conditions: Halts selection when identity cannot be established, evidence contradicts the target, or recency is being substituted for acceptance proof. - Use Case: After a bad deployment, use this Skill to inventory available snapshots and commits, verify which one was owner-accepted and runtime-verified, and hand the exact proven target to the restore process. ## Quick Start Ask the AI to evaluate the available backups and commits for the failed release and select a verified rollback target with its evidence.

Frequently Asked Questions about signalproof-rollback

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

FAQPage Schema
How do I choose a safe rollback target after a failed deployment?▼

Inventory all candidate backups, versions, and commits, then prefer owner-accepted or runtime-verified known-good baselines over the newest copies. Verify identity, completeness, and compatibility before selecting, and reject candidates known to have failed.

What is the difference between a backup and a verified rollback target?▼

A backup only proves bytes exist; a verified rollback target has established identity, completeness, compatibility, and recoverability evidence. Existence or recency of a backup does not prove it can be restored successfully.

Can I roll back to the most recent backup automatically?▼

No. Recency and names like 'backup', 'previous', or 'golden' are not acceptance evidence. The newest copy may contain the same failure; selection requires verified identity and recovery evidence or explicit risk acceptance.

When should a rollback selection be stopped instead of proceeding?▼

Stop when no trustworthy identity can be established, manifest evidence contradicts the claimed target, data or schema compatibility is materially unknown, or the only good copy would be consumed or overwritten by the attempt.

Does selecting a rollback target also perform the restore?▼

No. Selection does not grant overwrite or restore authority. The Skill returns the exact target, identity, evidence class, and limitations required by a separate Restore process.