archive

Move completed workflow artifacts into a dated archive bundle.

5|Updated Apr 29, 2026

Search Tags:#workflow #commit #claude code #idempotent #archive #git mv #file migration

Ready to run

npx skills add https://github.com/friedbotstudio/baseline --skill archive-friedbotstudio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/archive
Command: npx skills add https://github.com/friedbotstudio/baseline --skill archive-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes completed workflow artifacts from the active project tree so a commit can stay clean, organized, and free of work-in-progress files.

Core Features & Use Cases

Workflow Archiving: Moves slug-matched intake, brief, scout, research, spec, approval, swarm, and security artifacts into a dated archive bundle.
Git-Aware Relocation: Uses git moves when possible to preserve history and falls back to normal file moves when needed.
Conflict Protection: Refuses to overwrite existing archive contents and preserves partial progress for safe re-runs.
Use Case: After documentation is finished, archive all related artifacts for a feature slug so the repository is ready for the final commit step.

Quick Start

Use the archive skill to move the completed workflow artifacts for slug apollo into the appropriate dated archive bundle.

Frequently Asked Questions about archive

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

FAQPage Schema

How do I archive completed workflow artifacts before a git commit?▼

To archive completed workflow artifacts before a git commit, this Skill moves slug-matched intake, research, spec, and security files into a dated bundle. It uses git-aware relocation to preserve history and ensures your active project tree stays clean.

What is the best way to consolidate work-in-progress files for a clean commit?▼

Consolidating work-in-progress files for a clean commit involves moving completed workflow artifacts into a dated archive bundle. This removes temporary intake and spec files from the active tree while leaving workflow.json live until the final commit.

Does the archive process preserve git history when moving files?▼

Yes, the archive process preserves git history when moving files by using git moves when possible. If git moves are unavailable, it falls back to standard file moves while maintaining idempotent, move-only behavior for safe re-runs.

How do I handle file migration conflicts when archiving project artifacts?▼

When handling file migration conflicts during archiving, the Skill refuses to overwrite existing archive contents. This conflict protection preserves partial progress and ensures safe re-runs without losing previously archived data.

Can I use this archiving tool with Claude Code baseline workflows?▼

Yes, you can use this archiving tool with Claude Code baseline workflows. It targets workflows that finish document and commit phases and uses slug-based file discovery to consolidate intake, scout, research, spec, approval, swarm, and security files.

Why is workflow.json left live during the file migration process?▼

Workflow.json is left live during the file migration process to ensure the workflow remains active until the final commit step. The Skill archives completed document and phase artifacts while keeping the central configuration file available for ongoing operations.