wrap

Archive merged OpenSpec changes and clean up the workspace after a PR merges.

14|Updated Mar 23, 2026

Search Tags:#automation #git #archive #openspec #product-context #workspace-cleanup #post-merge

Ready to run

npx skills add https://github.com/memorysaver/agentic-engineering-patterns --skill wrap-memorysaver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/memorysaver/agentic-engineering-patterns/tree/main/skills/agentic-development-workflow/wrap
Command: npx skills add https://github.com/memorysaver/agentic-engineering-patterns --skill wrap-memorysaver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-merge archiving and workspace cleanup is error-prone and time-consuming when coordinating OpenSpec changes across parallel workspaces. This skill automates the end-to-end process to ensure a clean main branch and preserved history.

Core Features & Use Cases

Archive the merged OpenSpec changes on main using a controlled workflow.
Rebase and verify workspace state, stop dev servers, and commit/archive artifacts.
Clear the workspace and transfer lessons and status updates into product-context when in product-cycle mode.

Quick Start

Run wrap after a PR merges to archive the OpenSpec changes and tidy the workspace.

Frequently Asked Questions about wrap

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

FAQPage Schema

How do I automate post-merge archiving and workspace cleanup for OpenSpec changes?▼

Post-merge archiving and workspace cleanup is automated by coordinating fetch, rebase, archive, and workspace teardown to preserve history and keep the main branch clean.

What is the best way to archive OpenSpec changes after a PR merges?▼

The best way to archive OpenSpec changes is running an automated workflow that applies guardrails, stops dev servers, and commits artifacts via /opsx:archive on the main branch.

How does product-cycle mode update product-context.yaml during workspace cleanup?▼

In product-cycle mode, workspace cleanup transfers lessons and status updates directly into product-context.yaml to preserve the latest project state after the merge.

Can I use this to stop dev servers and clear parallel workspaces after a merge?▼

Yes, you can stop dev servers and clear parallel workspaces after a merge, as the workflow verifies workspace state, commits artifacts, and performs a full workspace teardown.