Agent Skills › dzhng/jevgrep › port-features

port-features

GitHub

用于将现有功能从上游仓库精确移植到目标环境，通过复制代码并保留历史逻辑而非重写，确保行为一致性和修复完整性。

.agents/skills/port-features/SKILL.md dzhng/jevgrep

Trigger Scenarios

需要将现有功能迁移到新框架或宿主环境要求精确复制已有功能以保留上游行为和修复

Install

npx skills add dzhng/jevgrep --skill port-features -g -y

More Options

Non-standard path

npx skills add https://github.com/dzhng/jevgrep/tree/main/.agents/skills/port-features -g -y

Use without installing

npx skills use dzhng/jevgrep@port-features

指定 Agent (Claude Code)

npx skills add dzhng/jevgrep --skill port-features -a claude-code -g -y

安装 repo 全部 skill

npx skills add dzhng/jevgrep --all -g -y

预览 repo 内 skill

npx skills add dzhng/jevgrep --list

SKILL.md

Frontmatter

{
    "name": "port-features",
    "description": "Port a feature from an existing repository by copying its actual code and editing the copy, so its bug fixes and behavioral nuances survive. Use when asked to copy or port an existing feature (especially an exact copy), when moving one into a different framework or host, or when a previous reimplementation missed upstream behavior."
}

Port Features

Upstream code is the spec. Every guard, ordering, timeout, and odd branch in it may be a bug fix someone already paid for. A rewrite from your understanding of the feature drops the ones you didn't notice.

Start from the code. Get a local checkout of upstream with its history, pin the exact commit, and read the feature's real files, not a screenshot, summary, or fetched snippet. Follow imports and callers until you know which files make up the feature.
Read the history. Read path-scoped git log, following renames, for those files, and read the fixes. Before changing or dropping anything that looks unnecessary, find out from history why it is there.
Copy, then edit. Copy the exact files, with their tests, into the destination first. Then delete what the destination does not need and change imports and host bindings. Keep upstream's structure and algorithms even where you would have written them differently. Never write your own version in their place.
Diff back. Diff the result against the pinned source and justify every change. When a carried-over test fails, fix the adapter before touching the algorithm or the test.

Done when the destination is the pinned upstream code plus a diff you can account for, and the handover names the upstream commit and every deliberate difference. Never call a rewrite a port.