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

Forward Port

by yamcodes in yamcodes/arkenv

Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

MITAuto-check passedBusiness, Finance & HR

Install Forward Port

skills CLI
$ npx skills add yamcodes/arkenv --skill forward-port -a claude-code

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

GitHub CLI
$ gh skill install yamcodes/arkenv forward-port --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/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/forward-port .claude/skills/forward-port && 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
forward-port
GitHub stars
145
Token cost
~970 tokens
SKILL.md length
414 words
Files
2
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

  • Works in 5 steps: Pick what to port (if not specified) → Gather source context → Adapt the implementation → …
  • A dev PR is merged and needs v1 parity
  • SKILL.md covers When to forward-port, Quick start, Workflow and Acceptance checklist, plus 2 more sections
  • Calls pnpm, git and gh

What it does

Forward Port is an agent skill from yamcodes/arkenv. Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names. Use when a dev PR is merged and needs v1 parity, when triaging "(v1)" reconciliation issues, or when the user mentions forward-porting, dual-tracking, or dev-to-v1 porting.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REFERENCE.md`).

It sits in Business, Finance & HR, covering Accounting and bookkeeping. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.

When your agent uses it

  • A dev PR is merged and needs v1 parity
  • Reconciliation issues
  • The user mentions forward-porting
  • Dev-to-v1 porting

Example prompts

  • “/forward-port”

Workflow steps

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

  1. Pick what to port (if not specified)
  2. Gather source context
  3. Adapt the implementation
  4. Port the changeset
  5. Verify and open PR

What it can do on your machine

Read from SKILL.md and the folder at commit 74b3732. 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:

    • pnpm
    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and 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

Forward Port loads about 970 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 414 words of instructions outside code blocks.

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

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 yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 414 words, ~970 tokens.

Download SKILL.mdSave it as .claude/skills/forward-port/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
forward-port
description
Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names. Use when a dev PR is merged and needs v1 parity, when triaging "(v1)" reconciliation issues, or when the user mentions forward-porting, dual-tracking, or dev-to-v1 porting.
metadata.internal
true

Forward-port (dev → v1)

ArkEnv runs dual-tracking: non-breaking work lands on dev (v0) first, then is manually adapted onto v1. Never merge dev into v1 wholesale - structural differences cause severe tree conflicts.

See REFERENCE.md for the full path/package map, changeset rename table, and real port examples.

When to forward-port

Forward-port after a merged dev PR that fixes a bug, adds a non-breaking feature, or updates shared integrations.

Skip forward-porting when work is (v1)-only, introduces dev-only structure, or should be implemented natively on v1.

Quick start

bash
gh pr view <number> --json title,mergeCommit,files
git fetch origin v1 && git checkout -b forward-port/<name> origin/v1
# adapt changes (workflow below)
pnpm run typecheck && pnpm run test
gh pr create --base v1 --title "fix: Forward-port <summary> from dev"

Workflow

0. Pick what to port (if not specified)

If the user did not name a PR, issue, or commit, stop and ask before writing code.

  1. Discover candidates - recently merged dev PRs that touch published packages and likely need v1 parity (see REFERENCE.md - discovery commands).
  2. Filter out PRs already forward-ported (v1 PR title/body mentions the dev PR, or commit message contains Forward-port).
  3. Present multiple choice via AskQuestion with up to 4 candidates. Label each option as #1234 - short title (packages touched).
  4. Always include "Other - I'll specify" as the last option so the user can paste a PR/issue number.
  5. If no candidates remain, say so and ask whether to port a specific PR/issue the user has in mind.

Do not guess or auto-pick when multiple candidates exist.

1. Gather source context

Read the merged dev PR: files, tests, changeset, linked issue. Note behavior - re-implement, don't blind cherry-pick. Map each touched package using REFERENCE.md.

Show full SKILL.md (173 more words)Show less
2. Adapt the implementation

Key path map:

devv1
packages/cli/src/**packages/arkenv/src/**
packages/arkenv/src/** (core)packages/core/src/**
nextjs, nuxt, build, …Same paths - verify imports

Checklist:

  • Fix imports (@arkenv/cli → arkenv, core → @arkenv/core)
  • Port tests and docs/examples if the dev PR touched them
  • Preserve v1-only decisions already on the branch (see REFERENCE)
3. Port the changeset

Rename frontmatter keys: "@arkenv/cli" → "arkenv", "arkenv" (core) → "@arkenv/core". Follow the changeset skill.

4. Verify and open PR

Run pnpm run typecheck, pnpm run test, and package-scoped tests if localized. Open PR targeting v1, link the dev PR and tracking issue.

Acceptance checklist

  • Behavior matches merged dev PR
  • No dev-only paths or imports remain
  • Changeset uses v1 package names
  • Tests pass on v1 branch

Common mistakes

MistakeFix
git merge dev into v1Feature-driven manual port
Blind cherry-pickRe-implement at v1 paths
"cli" in v1 changesetRename to "arkenv"
Core change in packages/arkenv/ on v1Core is packages/core/
Using the next npm tag on v1v1 publishes @alpha / @beta / @rc

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

Files

SKILL.md and 1 other file in skills/forward-port of yamcodes/arkenv.

  • SKILL.md
  • REFERENCE.md

Open the folder on GitHubat commit 74b3732

Compare with similar skills

Forward Port 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.

Forward Port compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Forward Port this skillyamcodes/arkenv145—~970Automated safety check: PassMIT
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Longbridge Value Investinghelsome/folio2692 repos~1.2kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence
Odoo Agency Fleet Reviewerpipe-org/mcp-odoo420—~699Automated safety check: PassMIT
Beancount Closebex-co/beancount-io295—~1.4kAutomated safety check: PassMIT

Similar skills

  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 5 days ago
    Business, Finance & HRAuto-check passed

  • Longbridge Value Investing

    helsome/folio

    Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.

    269 GitHub starsUsed in 2 repos~1.2k tokens
    Business, Finance & HRAuto-check passed

  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 16 days ago
    Business, Finance & HRAuto-check passed

  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    420 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

  • Beancount Close

    bex-co/beancount-io

    Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…

    295 GitHub stars~1.4k tokensUpdated today
    Business, Finance & HRAuto-check passed

  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    114 GitHub stars~15k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed

More from yamcodes/arkenv

All 20 skills in this repo

  • Hallmark

    yamcodes/arkenv

    Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.

    145 GitHub starsUsed in 4 repos~18k tokens
    Auto-check passed

  • Bulletproof React

    yamcodes/arkenv

    Bulletproof React architecture patterns for scalable, maintainable applications.

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

  • Arkenv

    yamcodes/arkenv

    Answer questions about ArkEnv and help implement environment variable validation.

    145 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Code Review

    yamcodes/arkenv

    Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

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

  • Groom Issue

    yamcodes/arkenv

    Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…

    145 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Internalize Skill

    yamcodes/arkenv

    Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal.

    145 GitHub stars~750 tokensUpdated today
    Auto-check passed

Categories

Questions about Forward Port

What does Forward Port do?

Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names. Forward Port is an agent skill from yamcodes/arkenv. Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

When should I use Forward Port?

Forward Port fits situations like: A dev PR is merged and needs v1 parity; reconciliation issues; the user mentions forward-porting; dev-to-v1 porting.

How do I install Forward Port in Claude Code?

Run `npx skills add yamcodes/arkenv --skill forward-port -a claude-code`. Or copy the skill folder (skills/forward-port in yamcodes/arkenv) into .claude/skills/forward-port in your project. Claude Code loads it when a task matches its description.

How do I install Forward Port in Codex?

Run `npx skills add yamcodes/arkenv --skill forward-port -a codex`. Or copy the skill folder (skills/forward-port in yamcodes/arkenv) into .agents/skills/forward-port in your project. Codex loads it when a task matches its description.

Can I use Forward Port 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 yamcodes/arkenv --skill forward-port -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/forward-port, .gemini/skills/forward-port, .github/skills/forward-port and .opencode/skills/forward-port in your project.

What does Forward Port need to run?

Going by SKILL.md and its folder, Forward Port needs the command-line tools its instructions call (pnpm, git and gh).

Does Forward Port access the network?

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

Is Forward Port 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 Forward Port use?

Forward Port 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 Forward Port use?

About 970 tokens (SKILL.md is roughly 3.9k 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 Forward Port?

Skills that share tags, products or a category with Forward Port: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Longbridge Value Investing (helsome/folio, 269 stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Forward Port?

yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

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