New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Porting Another Repository

by dyoshikawa in dyoshikawa/rulesync

Plan how to port a feature, configuration, or implementation from this repository into another repository.

MITAuto-check passedDevelopment

Install Porting Another Repository

skills CLI
$ npx skills add dyoshikawa/rulesync --skill porting-another-repository -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync porting-another-repository --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/porting-another-repository .claude/skills/porting-another-repository && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
porting-another-repository
GitHub stars
1.5k
Token cost
~1.1k tokens
SKILL.md length
548 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Plan how to port a feature, configuration, or implementation from this repository into another repository.

  • Works in 6 steps: Prepare the Output Directory → Analyze the Source (This Repository) → Analyze the Target Repository → …
  • Development work in your project
  • SKILL.md covers Step 0: Prepare the Output…, Step 1: Analyze the Source…, Step 2: Analyze the Target… and Step 3: Produce the Porting Plan, plus 2 more sections
  • Calls gh

What it does

Porting Another Repository is an agent skill from dyoshikawa/rulesync. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Model Context Protocol. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/porting-another-repository”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Prepare the Output Directory
  2. Analyze the Source (This Repository)
  3. Analyze the Target Repository
  4. Produce the Porting Plan
  5. Produce Concrete Diffs
  6. Write the Overview and Report

What it can do on your machine

Read from SKILL.md and the folder at commit 625bf98. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Porting Another Repository loads about 1.1k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 548 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 625bf98, republished under its MIT licence (© dyoshikawa). 548 words, ~1,080 tokens.

Download SKILL.mdSave it as .claude/skills/porting-another-repository/SKILL.md (or your agent's skills folder).
name
porting-another-repository
description
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.
targets
*

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 implement it.
  • Its dependencies within this repo (shared utilities, base classes, types, config) that would also need to come along.
  • Any build/test/tooling wiring it relies on (scripts, configs, fixtures, CI steps).
  • External package dependencies it pulls in.

Write the result to ${out}/01-source-analysis.md.

Step 2: Analyze the Target Repository

Understand the target's conventions so the port fits in naturally.

  • If target_repo is a local path, inspect it directly (grep/read).
  • If it is owner/repo or a URL, use gh repo view, gh api repos/<owner/repo>/contents/<path>, and the deepwiki MCP (mcp__deepwiki__ask_question, mcp__deepwiki__read_wiki_contents) to learn its structure.

Capture:

  • Language, package manager, build/test tooling, and directory layout.
  • Where the equivalent of the source feature would live in the target's structure.
  • Naming, style, and architectural conventions the port must follow.
  • Existing functionality that overlaps or conflicts with what is being ported.

Write the result to ${out}/02-target-analysis.md.

Show full SKILL.md (233 more words)Show less

Step 3: Produce the Porting Plan

Map source concepts onto the target. Use a small mapping table (source path/symbol → target path/symbol) — it is far easier to read than prose for this.

Cover:

  • A step-by-step sequence of changes, ordered so the target stays buildable.
  • Required dependency additions (with versions) and tooling/config changes.
  • Adaptations needed to match the target's conventions (renames, refactors, API shape changes).
  • Risks, open questions, and anything deliberately out of scope.
  • A short test/verification plan for the target.

Write the result to ${out}/03-porting-plan.md.

Step 4: Produce Concrete Diffs

For each step in the plan, write the concrete code/config the user should add to the target, in fenced blocks labeled with their target file paths. Where an existing target file changes, show a unified-diff-style snippet. Keep these ready to copy-paste.

Write the result to ${out}/04-diff.md.

Step 5: Write the Overview and Report

Write ${out}/00-overview.md last, as the index for the run. It must contain:

  • Source repo and scope, target repo, and the timestamp.
  • A one-paragraph summary of what is being ported and the recommended approach.
  • A links list to the other files (01-source-analysis.md … 04-diff.md) with a one-line description of each.
  • Top risks and open questions surfaced during the analysis.

Then report to the user:

  • The absolute path of ${out}/.
  • A one-line summary of the port (what moves, where it lands).
  • The top open questions the user needs to decide before applying the plan.

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/porting-another-repository of dyoshikawa/rulesync.

Open the folder on GitHubat commit 625bf98

Compare with similar skills

Porting Another Repository next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Porting Another Repository compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Porting Another Repository this skilldyoshikawa/rulesync1.5k—~1.1kAutomated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Analyze Logsactivepieces/activepieces25k1 repos~1.6kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Claude Code Skillcodeaashu/claude-code3.4k1 repos~2.7kAutomated safety check: PassProprietary

Similar skills

  • Debugging Executions

    n8n-io/n8n

    Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Analyze Logs

    activepieces/activepieces

    Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.

    25k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • Run Nx Generator

    nrwl/nx

    Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes

More from dyoshikawa/rulesync

All 40 skills in this repo

  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Commit Push PR

    dyoshikawa/rulesync

    Commit current changes, push to remote, and create or update a pull request.

    1.5k GitHub stars~458 tokensUpdated today
    Auto-check passed

  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Porting Another Repository

What does Porting Another Repository do?

Plan how to port a feature, configuration, or implementation from this repository into another repository. Porting Another Repository is an agent skill from dyoshikawa/rulesync. Plan how to port a feature, configuration, or implementation from this repository into another repository.

When should I use Porting Another Repository?

Porting Another Repository fits situations like: development work in your project.

How do I install Porting Another Repository in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill porting-another-repository -a claude-code`. Or copy the skill folder (.rulesync/skills/porting-another-repository in dyoshikawa/rulesync) into .claude/skills/porting-another-repository in your project. Claude Code loads it when a task matches its description.

How do I install Porting Another Repository in Codex?

Run `npx skills add dyoshikawa/rulesync --skill porting-another-repository -a codex`. Or copy the skill folder (.rulesync/skills/porting-another-repository in dyoshikawa/rulesync) into .agents/skills/porting-another-repository in your project. Codex loads it when a task matches its description.

Can I use Porting Another Repository in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill porting-another-repository -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/porting-another-repository, .gemini/skills/porting-another-repository, .github/skills/porting-another-repository and .opencode/skills/porting-another-repository in your project.

What does Porting Another Repository need to run?

Going by SKILL.md and its folder, Porting Another Repository needs the command-line tools its instructions call (gh).

Does Porting Another Repository access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Porting Another Repository safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Porting Another Repository use?

Porting Another Repository is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Porting Another Repository use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Porting Another Repository?

Skills that share tags, products or a category with Porting Another Repository: Debugging Executions (n8n-io/n8n, 207k stars), ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars), Analyze Logs (activepieces/activepieces, 25k stars) and Release (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Porting Another Repository?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,509 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.