archive

Merge feature deltas into full specs and designs with review and version control.

8|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zxdxjtu/harness --skill archive-zxdxjtu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/zxdxjtu/harness/tree/main/skills/archive
Command: npx skills add https://github.com/zxdxjtu/harness --skill archive-zxdxjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive consolidates incremental feature deltas into the full spec and design documents, enabling deterministic review and safe evolution.

Core Features & Use Cases

  • Merge Spec Delta into Full Spec: Read incremental specs and integrate into full spec, updating existing sections while preserving content.
  • Merge Design Delta into Full Design: Incorporate design changes into the full design, updating dependency graphs and data models.
  • Final Code Review & Atomic Commits: Run a code review pass, split changes into atomic commits, and prepare for push and MR.
  • Evolution & Archival Triggers: Log evolution data and trigger subsequent self-evolution steps.

Quick Start

Run the archive workflow after a feature is ready to merge deltas, perform reviews, and trigger self-evolution.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I merge incremental feature deltas into full spec and design documents?

To merge feature deltas into full specs and designs, you can automate the integration process to update existing sections, dependency graphs, and data models while preserving original content. This ensures deterministic review and safe evolution.

What is the best way to automate code review and plan atomic commits for merge requests?

Automating code review and planning atomic commits involves running a final review pass on integrated changes, splitting them into atomic commits, and preparing the results for pushing and creating merge requests.

How does recording evolution data work after merging design changes?

Recording evolution data works by logging metadata and triggering subsequent self-evolution steps after design deltas are safely integrated into the full design, ensuring changes are tracked across modules.

When do I need to run the archive workflow for development projects?

You need to run the archive workflow after a feature is ready to merge deltas, perform reviews, and trigger self-evolution. It is applied when incremental changes must be safely integrated across modules.

Can I update dependency graphs and data models when incorporating design deltas?

Yes, incorporating design deltas into the full design automatically updates dependency graphs and data models. The workflow ensures incremental design changes are integrated while preserving existing content structure.