abort

Name: abort
Availability: InStock
Author: duongtdn

Terminate devloop executions by cleaning locks, state files, and optionally preserving work as draft pull requests.

Updated Jul 6, 2026

Search Tags:#automation #git #workflow #github #cleanup #devloop

Ready to run

npx skills add https://github.com/duongtdn/devloop --skill abort

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: abort
Source: https://github.com/duongtdn/devloop/tree/main/skills/abort
Command: npx skills add https://github.com/duongtdn/devloop --skill abort

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a safe, conversational escape hatch for stopping an in-progress devloop execution, ensuring that your working branch, state files, and locks are handled predictably without leaving your repository in a corrupted state.

Core Features & Use Cases

Execution Cleanup: Safely tears down active run artifacts including locks and state files.
Branch Management: Offers flexible options to delete, keep, or park your work as a draft PR before stopping.
Safety Guards: Prevents accidental deletion of work by requiring explicit confirmation and checking for live process locks.

Quick Start

Use the abort skill to stop the current devloop run and keep the work in a draft pull request.

Frequently Asked Questions about abort

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

FAQPage Schema

How do I safely stop an active devloop run without corrupting my git repository?▼

To safely stop an active devloop run, you can use an abort process that tears down execution artifacts, manages state file cleanup, and releases GitHub issue locks while preserving branch integrity.

Can I save my work to a draft pull request before stopping a workflow execution?▼

Yes, you can preserve your work by parking the branch as a draft pull request before stopping the workflow execution, ensuring your changes are safely stored on the remote repository rather than deleted.

What happens to branch artifacts and state files when terminating a GitHub automation session?▼

Terminating a GitHub automation session cleans up active run artifacts by deleting or parking branch references and clearing state files, which prevents stale locks and keeps the repository status predictable.

Do I need explicit confirmation to delete working branches during a devloop cleanup?▼

Yes, devloop cleanup requires explicit confirmation to delete working branches, acting as a safety guard to prevent accidental data loss when checking for and releasing live process locks.

Does stopping an in-progress workflow execution require specific git or GitHub integrations?▼

Yes, stopping an in-progress workflow execution requires git integration and GitHub MCP access to verify repository status, manage remote branch references, and operate within specific GitHub issue contexts.

Why does an aborted devloop execution leave locks behind on my repository?▼

An aborted devloop execution might leave locks behind if the cleanup process is interrupted, but a proper abort skill explicitly releases these locks and clears state files to prevent a corrupted repository state.