port-from-sibling

Stars2

Forks0

UpdatedJuly 26, 2026 at 03:24

Carry a config, pattern, or workflow from a sibling repository into this one. Use whenever a request references another local repo by relative path ("like ../calcipy", "see ../yak-shears/hk.pkl", "the way ../my-go-template does it"), or when migrating a project onto tooling another project already uses.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

KyleKing

KyleKing/dotfiles

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	port-from-sibling
description	Carry a config, pattern, or workflow from a sibling repository into this one. Use whenever a request references another local repo by relative path ("like ../calcipy", "see ../yak-shears/hk.pkl", "the way ../my-go-template does it"), or when migrating a project onto tooling another project already uses.

Port from a sibling repo

The user keeps many small repos plus two copier templates (calcipy_template for Python, my_go_template for Go) and propagates changes in both directions. The reusable part of that work is the checklist, not the copying.

Procedure

Read the reference in full. Not just the file named — its config, its lockfile pins, and any AGENTS.md, CLAUDE.md, or ADR that explains why it is shaped that way. Reading the file alone reproduces the shape and loses the reason.
Diff against local. State what already exists here, what conflicts, and what is genuinely missing. A migration usually turns out to be smaller than it looked.
Adapt, do not copy. The reference repo has a different name, language version, dependency set, and CI. Strip what is specific to it. A pasted config that names the wrong package is worse than none.
Note where the two have deliberately diverged. If local does something differently on purpose, say so and ask before overwriting it. Do not silently converge them.
Run it. The pre-commit hook, the lint step, the test suite — whatever the ported config claims to do. A config that evaluates is not a config that works.

Push it back upstream

The step most often forgotten. When the change is a general improvement rather than project-specific, it belongs in the template so every future project gets it:

Python tooling changes go to ../calcipy_template/package_template
Go tooling changes go to ../my_go_template
Web app scaffolding goes to ../app-template, with rendered output regenerated under .ctt/

Say explicitly whether the change should propagate upstream, and ask if it is not clear. Do not commit to the template repo without being asked.

Direction matters

Porting template to project is a copier update — use the copier-template skill rather than hand-copying, so .copier-answers.yml stays truthful.

Porting project to template is manual, and needs the specifics generalized back into {{ }} placeholders.

Porting project to project is the plain case this skill covers.

More from this repository

same repository

browser-screenshots

KyleKing/dotfiles

Capture and persist browser screenshots or GIFs for visual review of a web UI. Use when verifying a UI change visually, reviewing a page's design or layout, recording a multi-step interaction (dropdown, hover, form flow), toggling dark mode for a comparison shot, or when a screenshot needs to be written to disk rather than only shown inline.

2026-07-262

copier-template

KyleKing/dotfiles

Run and troubleshoot copier updates in a project generated from one of the user's templates, and maintain the templates themselves. Use when a task mentions copier, copier update, .copier-answers.yml, .rej files after an update, ctt or copier-template-tester, or one of calcipy_template, mdformat-plugin-template, my_go_template, or app-template.

2026-07-262

hk-config

KyleKing/dotfiles

Audit or write an hk.pkl config (jdx/hk git hooks). Use when creating hk.pkl, upgrading the pinned hk version, adding a linter step, or when fixes made by a pre-commit hook are not being staged. Covers version pinning, staging semantics, builtins, and DRY structure.

2026-07-262

observability-clis

KyleKing/dotfiles

Query PostHog error tracking and Sentry issues from the command line. Use when asked what errors are happening, which errors are being missed or untriaged, for production error rates or impact by user, or whenever posthog-cli or sentry-cli is mentioned.

2026-07-262

orchestrate

KyleKing/dotfiles

Work a multi-phase plan to completion with subagents, checkpoint commits, and questions back to the user. Invoke explicitly with a plan document.

2026-07-262

python-async

KyleKing/dotfiles

Async Python conventions and footguns — asyncio.TaskGroup over gather, event-loop-bound primitives, offloading blocking work to threads or processes, cancellation across the thread boundary, and dedicated executors. Use when writing or reviewing async def, await, asyncio.to_thread, run_in_executor, create_task, async generators, or when diagnosing a stalled event loop, a "bound to a different event loop" error, or latency that only appears under load.

2026-07-262

name	port-from-sibling
description	Carry a config, pattern, or workflow from a sibling repository into this one. Use whenever a request references another local repo by relative path ("like ../calcipy", "see ../yak-shears/hk.pkl", "the way ../my-go-template does it"), or when migrating a project onto tooling another project already uses.

Port from a sibling repo

Procedure

Read the reference in full. Not just the file named — its config, its lockfile pins, and any AGENTS.md, CLAUDE.md, or ADR that explains why it is shaped that way. Reading the file alone reproduces the shape and loses the reason.
Diff against local. State what already exists here, what conflicts, and what is genuinely missing. A migration usually turns out to be smaller than it looked.
Adapt, do not copy. The reference repo has a different name, language version, dependency set, and CI. Strip what is specific to it. A pasted config that names the wrong package is worse than none.
Note where the two have deliberately diverged. If local does something differently on purpose, say so and ask before overwriting it. Do not silently converge them.
Run it. The pre-commit hook, the lint step, the test suite — whatever the ported config claims to do. A config that evaluates is not a config that works.

Push it back upstream

The step most often forgotten. When the change is a general improvement rather than project-specific, it belongs in the template so every future project gets it:

Python tooling changes go to ../calcipy_template/package_template
Go tooling changes go to ../my_go_template
Web app scaffolding goes to ../app-template, with rendered output regenerated under .ctt/

Say explicitly whether the change should propagate upstream, and ask if it is not clear. Do not commit to the template repo without being asked.

Direction matters

Porting template to project is a copier update — use the copier-template skill rather than hand-copying, so .copier-answers.yml stays truthful.

Porting project to template is manual, and needs the specifics generalized back into {{ }} placeholders.

Porting project to project is the plain case this skill covers.