porting-another-repository
Plan how to port a feature, configuration, or implementation from this repository into another repository. Analyzes the source feature here and the target repo's conventions, then writes a multi-file porting plan (overview, source analysis, target analysis, plan, diff) to tmp/porting-another-repository-{YYYYMMDD-HHmm}/*.md for the user to review and apply manually.
Profile →npx skills add dyoshikawa/rulesync --skill porting-another-repository --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
arguments = the user's request Parse `arguments` as: - `target_repo`: the repository to port INTO, in `owner/repo` form, a URL, or a local path - `scope`: what to port from THIS repository (a feature name, directory, file, or rough description) If `target_repo` is not provided, ask the user which repository to port into. If `scope` is not provided, ask the user what part of this repository they want to port. The direction is fixed: the **source** is this repository, the **target** is `target_repo`. This skill never modifies the target repository directly — it only produces a porting plan on disk for the user to apply manually. ## Step 0: Prepare the Output Directory Compute a single timestamp once and reuse it for every file: ```bash ts="$(date +%Y%m%d-%H%M)" out="tmp/porting-another-repository-${ts}" mkdir -p "${out}" ``` All artifacts in this run go under `${out}/`. Do not recompute the timestamp per file — every file must share the same directory. ## Step 1: Analyze the Source (This Repository) Understand exactly what is being ported. Prefer targeted symbol and search tools over reading whole files. Identify, for the requested `scope`: - The entry points and the files that imple
- Step 0: Prepare the Output Directory
- Step 1: Analyze the Source (This Repository)
- Step 2: Analyze the Target Repository
- Step 3: Produce the Porting Plan
- Step 4: Produce Concrete Diffs
- Step 5: Write the Overview and Report
mkdir -p "${out}"What does the porting-another-repository skill do?
Plan how to port a feature, configuration, or implementation from this repository into another repository. Analyzes the source feature here and the target repo's conventions, then writes a multi-file porting plan (overview, source analysis, target analysis, plan, diff) to tmp/porting-another-repository-{YYYYMMDD-HHmm}/*.md for the user to review and apply manually.
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill porting-another-repository --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.