Menu

Individual skill

port-features

0upvotes

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.

skills/engineering/port-features/SKILL.md

Read pinned source

Source commit 0867285d3f2612104afa6bb774779943854d4c15

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,470
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.

1. **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.
2. **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.
3. **Copy, then edit.** Copy the exact files, with their tests, into the
Back to top