kf-revert

Revert Kiloforge tracks, phases, or tasks using git-aware operations.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-revert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kf-revert
Source: https://github.com/Kiloforge/kiloforge-skills/tree/main/kf-revert
Command: npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-revert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables undo of changes in Kiloforge by targeting logical work units (track, phase, or task) with git-aware operations, reducing risk of manual rework and drift.

Core Features & Use Cases

  • Revert entire tracks, individual phases, or specific tasks while preserving history and track.yaml integrity.
  • Automates safety checks and pre-flight validations before performing reverts.
  • Supports guided recovery and status restoration to a pending state after reverts.

Quick Start

Run the revert command with a trackId to revert the entire track, or specify a phase or task reference to revert a subset.

Frequently Asked Questions about kf-revert

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

FAQPage Schema
How do I revert changes to a specific task or phase in a git workflow?

You can revert changes by targeting logical work units like specific tasks or phases using git-aware operations. The system applies pre-flight checks to preserve history and track.yaml integrity during the reversion process.

Can I undo an entire track without losing git history?

Yes, you can revert entire tracks while preserving git history and track.yaml integrity. The process automates safety validations before performing reverts to prevent unintended data loss.

What is the best way to safely undo track-level work in Kiloforge?

The safest way to undo track-level work is using git-aware revert operations that target logical work units. This approach runs pre-flight validations and guided recovery to restore status to a pending state safely.

Does the revert process require manual updates to track.yaml?

No, the git-aware reversion process automatically handles track.yaml updates. It preserves configuration integrity while reverting tracks, phases, or tasks without requiring manual file edits.

What happens to task status after reverting a phase or track?

After reversion, the system supports guided recovery and status restoration to a pending state. This ensures the workflow remains consistent and allows you to reattempt the reverted work.

Are there limitations or risks when reverting changes across multiple phases?

The main risk is unintended data loss, which the system mitigates through strict input validation and pre-flight safety checks. You should ensure clear references are provided before initiating any reversion.