skills.rest
augentic
augenticOFFICIAL
Explore all skills by this author →
WebsiteGitHub

abandon

Abandon development changes by updating status and archiving directories.

1|Updated Mar 4, 2026
Search Tags:#git#workflow#development#version control#discard#abandon change
One-click install
npx skills add https://github.com/augentic/specify --skill abandon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: abandon
Source: https://github.com/augentic/specify/tree/main/plugins/spec/skills/abandon
Command: npx skills add https://github.com/augentic/specify --skill abandon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows users to easily discard a work-in-progress change that should not be finalized or merged into the main codebase.

Core Features & Use Cases

  • Discard Changes: Safely abandon any active development change.
  • Prevent Accidental Merges: Ensures that incomplete or unwanted changes are not accidentally archived.
  • Use Case: You started implementing a feature but realized it's not feasible or the requirements changed drastically. Use this Skill to cleanly remove the work without affecting the baseline.

Quick Start

Abandon the current change.

Frequently Asked Questions about abandon

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

FAQPage Schema
How do I discard a git change without merging it into the baseline?▼

To discard a git change without merging it into the baseline, the Skill updates the change's status to 'abandoned' and moves its directory to an archive location, preventing specs from merging.

What happens to abandoned development changes in version control?▼

Abandoned development changes are moved to an archive location within the .specify/changes/ directory and their status is updated to 'abandoned', ensuring they are not finalized or merged into the main codebase.

How do I safely remove a work-in-progress feature from my development workflow?▼

You can safely remove a work-in-progress feature by abandoning the change, which handles confirmation prompts for user safety and moves the directory to an archive location without affecting the baseline.

Do I need to resolve schemas before discarding a change in version control?▼

Yes, schema resolution is required for validation before discarding a change, ensuring the change is correctly identified and processed within the .specify/changes/ directory structure.

Can I prevent accidental merges of incomplete changes into the main codebase?▼

Yes, you can prevent accidental merges by abandoning the incomplete change, which updates its status to 'abandoned' and moves it to an archive location, stopping it from being merged into the baseline.

Why does discarding a change require confirmation prompts?▼

Discarding a change requires confirmation prompts for user safety, ensuring that work-in-progress changes are not accidentally or unintentionally abandoned before their directory is moved to an archive location.

Related Skills

Explore More Software Engineering Skills→
augenticaugentic
1

status

Display Specify change lifecycle, artifact completion, and task progress.

Official
Intermediate
open-platform-modelopen-platform-model

openspec-harmonize-changes

Detect conflicting OpenSpec changes and generate a structured harmony report.

Official
Advanced
bvshibvshi

10x-archive

Archive completed change folders and update status in a git repository.

Community
Intermediate
Haohao-endHaohao-end
779

git-guardrails-claude-code

Classify destructive Git commands and warn about irreversible risks.

Community
Intermediate