skills.rest
happier-dev
happier-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

happier-port-0-2-to-0-3

Ports validated Happier 0.2 changes into the evolved 0.3 codebase by intent.

1.6k|141|Updated Dec 16, 2025
Search Tags:#Git#regression prevention#Refactoring#happier#release branches#Code Migration#forward-port
One-click install
npx skills add https://github.com/happier-dev/happier --skill happier-port-0-2-to-0-3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: happier-port-0-2-to-0-3
Source: https://github.com/happier-dev/happier/tree/main/skills/happier-port-0-2-to-0-3
Command: npx skills add https://github.com/happier-dev/happier --skill happier-port-0-2-to-0-3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Forward-porting changes between diverging release lines often leads to blind cherry-picks, overwritten evolved code, or silently dropped fixes. This Skill provides a disciplined workflow for moving a complete, validated 0.2 change into the 0.3 line by intent rather than by filename, without regressing 0.3 architecture or unrelated work.

Core Features & Use Cases

  • Intent-based port mapping: Classifies every source behavior as already satisfied, adaptable, broadened, or not applicable in 0.3, with evidence.
  • Architecture re-discovery: Locates the current 0.3 canonical owner, sibling consumers, and compatibility seams instead of trusting matching filenames.
  • Safe worktree handling: Preserves unrelated dirty destination bytes, never stages or commits, and reports exact changed paths to the calling workflow.
  • Use Case: A bug fix landed on the 0.2 branch of Happier and must reach 0.3, where the owning module was refactored. The Skill re-discovers the new owner, adapts the fix through 0.3 abstractions, and proves it with RED -> GREEN tests.

Quick Start

Use the happier-port-0-2-to-0-3 skill to port this validated 0.2 change into the 0.3 checkout without overwriting evolved code.

Frequently Asked Questions about happier-port-0-2-to-0-3

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

FAQPage Schema
How do I port a change from an old release branch to a refactored codebase?▼

Port by intent, not by filename: record each source behavior's outcome, owner, and tests, then re-discover the destination's canonical owner and adapt the change through its existing abstractions. This Skill structures that analysis and requires RED to GREEN test evidence for behavior changes.

How to forward-port fixes without overwriting newer code?▼

Treat the destination worktree as shared and dirty: inspect current bytes before editing, layer changes onto the live worktree, and never copy whole files or restore old owners. The Skill classifies each intent as already satisfied, adapted, broadened, or not applicable before any edit.

Does this skill commit or merge changes between branches?▼

No. The Skill never stages, commits, cherry-picks, or merges. It applies adapted edits to the destination worktree and reports exact changed paths and validation results, leaving commit authority, grouping, and messages to the calling workflow.

What happens if the 0.3 destination checkout is not available?▼

The Skill first tries an explicitly supplied destination, then an optional verified sibling alias such as ../v0.3.x. If neither resolves to a valid Git checkout, it continues source-side analysis and reports the port as blocked with the exact missing location.

When should a 0.2 change not be ported to 0.3?▼

Skip porting when the intent is already satisfied in 0.3 with evidence, or when the code path is unreachable or deliberately replaced. Test-only source follow-ups may also need no destination edit if 0.3 already proves the contract.

Related Skills

Explore More Software Engineering Skills→
openchamberopenchamber
9.5k

openchamber-change-discipline

Guides risk-classified code changes with scoped validation across OpenChamber workspaces.

Official
Intermediate
skrrt-shskrrt-sh
2

commit

Group git changes into focused commits with mandatory gitmojis and conventional-commit structure.

Official
Advanced
hpsgdhpsgd

identity-verification

Verify identity claims across multiple independent public sources.

Official
Advanced
GaoZimeng0425GaoZimeng0425
6

git-advanced-workflows

Rebase, cherry-pick, bisect, manage worktrees, and inspect reflog in Git.

Community
Advanced