port-from-archive

Port archived feature behavior into the current codebase while preserving invariants.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/DotanVG/Orbital-Breach --skill port-from-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: port-from-archive
Source: https://github.com/DotanVG/Orbital-Breach/tree/main/.claude/skills/port-from-archive
Command: npx skills add https://github.com/DotanVG/Orbital-Breach --skill port-from-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Port a feature from archived branches into the current Orbital Breach codebase without breaking current invariants.

Core Features & Use Cases

  • Safely port archived features by inspecting the archived version and the current target code.
  • Ensure invariants are preserved and only the necessary behavioral changes are ported.
  • Use as a guide during code migration to minimize regressions and maintain architecture consistency.

Quick Start

Port a specific archived feature by inspecting the archived file with git show archive/dev:<path>, compare it to the target files, and port only the necessary behavior while preserving current invariants.

Frequently Asked Questions about port-from-archive

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

FAQPage Schema
How do I port a feature from an archived git branch into my current codebase?

Porting archived features requires inspecting archived files with git show, comparing them to live code, and selectively migrating behavior while validating against existing invariants to prevent regressions.

What is the safest way to revive archived code without breaking invariants?

The safest way to revive archived code is to inspect the archived version, compare it to live code, and port only necessary behavioral changes while validating against existing invariants and tests.

How do I compare archived files with my active codebase during code migration?

During code migration, compare archived files with your active codebase by inspecting the archived version with git show archive/dev:<path> and evaluating it against the live target files.

Can I reintroduce an archived feature into my active development branch without regressions?

Reintroducing an archived feature without regressions requires porting only the necessary behavior and validating the changes against existing invariants and tests in the active branch.

When should I selectively port behavior instead of merging an entire archived branch?

Selectively port behavior instead of merging an entire archived branch during code maintenance or disaster recovery, when preserving current invariants and minimizing regressions is your priority.