skills.rest
memorysaver
memorysaverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

aep-wrap

Archive OpenSpec changes and clean up the workspace after a pull request merge.

Updated May 18, 2026
Search Tags:#git#cleanup#archiving#post-merge#feature lifecycle
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill aep-wrap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aep-wrap
Source: https://github.com/memorysaver/project-understanding/tree/main/.agents/skills/aep-wrap
Command: npx skills add https://github.com/memorysaver/project-understanding --skill aep-wrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the archiving of OpenSpec changes and cleanup of the workspace after a pull request has been merged, streamlining the feature lifecycle.

Core Features & Use Cases

  • Post-Merge Archive: Archives the OpenSpec changes after a pull request merge.
  • Workspace Cleanup: Removes the workspace and cleans up after the merge.
  • Use Case: After a pull request is merged into the integration branch, this Skill can be used to automate the process of archiving the changes and cleaning up the workspace.

Quick Start

Run the 'aep-wrap' command after a PR has been merged or when prompted with 'wrap up', 'archive', 'cleanup after merge', or 'post-merge'.

Frequently Asked Questions about aep-wrap

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

FAQPage Schema
How do I automate post-merge cleanup and archiving for feature branches?▼

Post-merge cleanup can be automated by running scripts that archive OpenSpec changes and remove the workspace after a pull request is merged into the integration branch.

What is the best way to archive OpenSpec changes after a pull request merge?▼

Archiving OpenSpec changes after a merge is handled by executing automated scripts that process the feature changes and clean up the associated workspace.

Do I need git to clean up a workspace and archive changes after a merge?▼

Yes, you need git to perform post-merge workspace cleanup and archiving, as the process relies on git commands for branch operations, file management, and commit handling.

How does feature lifecycle cleanup work after integrating a pull request?▼

Feature lifecycle cleanup works by archiving the integrated changes and removing the redundant workspace, streamlining the transition from active development to project archiving.

Can I trigger workspace cleanup automatically when a feature is wrapped up?▼

Yes, workspace cleanup is triggered automatically when prompted with phrases like 'wrap up', 'archive', 'cleanup after merge', or 'post-merge' during your workflow.

What are the limitations of using scripts for post-merge git branch operations?▼

The cleanup scripts are limited to environments with git installed and are specifically designed for archiving OpenSpec changes, requiring proper execution of branch operations and file management commands.

Related Skills

Explore More Software Engineering Skills→
lklimeklklimek
1

merge-base

Automate Git merges with conflict resolution and behavioral change reports.

Community
Advanced
chenxingqiangchenxingqiang

draft-release-notes

Generate release notes drafts from structured changelog data.

Community
Intermediate
dxc-dannydxc-danny
8

finishing-a-development-branch

Validate tests and guide merge or PR decisions for Git feature branches.

Community
Advanced
otrebuotrebu
2

eval-test-skill

List and delete merged Git branches with user confirmation.

Community
Basic