Agent skill

Port Engine Changes

by nordstjernen-web in nordstjernen-web/northstar-browser

Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction.

GPL-3.0Auto-check passedTesting & QA

Install Port Engine Changes

skills CLI
$ npx skills add nordstjernen-web/northstar-browser --skill port-engine-changes -a claude-code

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

GitHub CLI
$ gh skill install nordstjernen-web/northstar-browser port-engine-changes --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/nordstjernen-web/northstar-browser.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/port-engine-changes .claude/skills/port-engine-changes && 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
port-engine-changes
GitHub stars
127
Token cost
~1.1k tokens
SKILL.md length
625 words
Files
2
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction.

  • Works in 3 steps: Compare commit subjects only to… → Confirm presence or absence by searching… → Discard anything the destination…
  • Cherry-picks where the two trees share most engine sources but differ in features
  • SKILL.md covers Establish what is already there, Check applicability before…, Expect edition-specific breakage and Verify in the destination, not…, plus 2 more sections
  • Calls git

What it does

Port Engine Changes is an agent skill from nordstjernen-web/northstar-browser. Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction. Use for backports, forward-ports, and cherry-picks where the two trees share most engine sources but differ in features, helpers, or vendored dependencies.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA. The repository describes itself as: Northstar web browser, Open Source License: GPL v3. Northstar web browser is a real web browser, not based on Firefox or Chrome. The licence is GPL-3.0.

When your agent uses it

  • Cherry-picks where the two trees share most engine sources but differ in features
  • Vendored dependencies

Example prompts

  • “/port-engine-changes”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Compare commit subjects only to shortlist candidates. The same fix often lands in both trees under different wording, so a subject that…
  2. Confirm presence or absence by searching the destination for the code the change introduces — a new function, field, or predicate — not by…
  3. Discard anything the destination excludes by policy: features the scope forbids, dependencies it vendors differently, and modules it does…

What it can do on your machine

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

    • git

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

  • Network

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

Port Engine Changes loads about 1.1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 625 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
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 nordstjernen-web/northstar-browser at commit 98475ea, republished under its GPL-3.0 licence (© nordstjernen-web). 625 words, ~1,127 tokens.

Download SKILL.mdSave it as .claude/skills/port-engine-changes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
port-engine-changes
description
Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction. Use for backports, forward-ports, and cherry-picks where the two trees share most engine sources but differ in features, helpers, or vendored dependencies.

Port Engine Changes Between Editions

Read the repository instructions of the destination tree first. Preserve unrelated changes. The source commit is evidence, not authority: it was verified against a different tree.

Establish what is already there

  1. Compare commit subjects only to shortlist candidates. The same fix often lands in both trees under different wording, so a subject that looks absent may already be present.
  2. Confirm presence or absence by searching the destination for the code the change introduces — a new function, field, or predicate — not by trusting the log.
  3. Discard anything the destination excludes by policy: features the scope forbids, dependencies it vendors differently, and modules it does not build.

Check applicability before committing to it

Generate a patch from the source commit and test it against the destination:

sh
git format-patch -1 <commit> --stdout -- src/ > /tmp/port.patch
git apply --check /tmp/port.patch

Prefer this to adding a remote for the other tree: it keeps the histories separate and makes divergence visible immediately. A patch that does not apply is a signal to port by hand, not to force it.

Expect edition-specific breakage

A change that compiles in one tree can fail in the other because the destination lacks a helper the source takes for granted, declares it later in the file, or gives it a different signature. Compilers report this as an implicit declaration followed by a conflicting redeclaration, and the symbol then fails to link.

Before porting, resolve every function the change calls against the destination. When a helper is missing, either lift it out of the destination's own equivalent code or express the call through primitives the destination already has. Do not copy a helper that duplicates one the destination spells differently.

Verify in the destination, not the source

Compiling the changed translation units alone is not sufficient: it misses missing declarations in other units, link errors, and header drift. Build the whole destination tree.

Work in a clean worktree checked out at the destination's published head so a shared or mid-edit working tree cannot contaminate the result:

sh
git worktree add --detach <tmp> origin/main

Then exercise the behavior the change is supposed to alter, and confirm it differs from the unported build in the direction the source commit claims. A port that builds but changes nothing observable has not been verified.

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

Record the origin

Name the source commit in a Ported-From: <owner>/<repo>@<full sha> trailer, taking the sha from git rev-parse rather than typing it, and describe the behavior in the destination's own terms. When the source carries a Security-Fix: slug, keep it; when it is a security fix without one, give the port a new slug. Both trailers belong in the final trailer block next to Co-Authored-By, where git interpret-trailers finds them. Do not copy a message that refers to code, tests, or scores that do not exist in the destination.

Northstar context

Northstar is the purist GPL edition of Nordstjernen; the engine sources are largely shared, but code crosses into Northstar only under the provenance rules in AGENTS.md: from Nordstjernen and Southstar only the copyright holder's own commits, never an external contributor's without their written GPL license. Check the author of every source commit before checking applicability, and stop if it fails. A Claude-authored commit can still build on code an outside contributor wrote; port only the parts that stand without it. Both trees are edited continuously, so re-read the destination head immediately before porting.

Differences that break ports in practice: Northstar consumes quickjs-ng as an upstream meson subproject and carries no in-tree engine fork, so changes that patch a vendored JavaScript engine do not apply; the features the repository instructions exclude from this edition are absent here; and helper availability in src/js.c differs between the trees even where the surrounding code matches.

Push only to the destination's own remote. Never push one edition's history to the other's.

© nordstjernen-web, GPL-3.0. 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 .agents/skills/port-engine-changes of nordstjernen-web/northstar-browser.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 98475ea

Compare with similar skills

Port Engine Changes 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.

Port Engine Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Port Engine Changes this skillnordstjernen-web/northstar-browser127—~1.1kAutomated safety check: PassGPL-3.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed
  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-check passed

More from nordstjernen-web/northstar-browser

  • Audit Browser Security Boundaries

    nordstjernen-web/northstar-browser

    Audit browser-engine changes that process untrusted content or cross native-memory, origin, network, storage, extension, decoder, sandbox, or operating-system boundaries.

    127 GitHub stars~920 tokensUpdated today
    Auto-check passed
  • Build Northstar

    nordstjernen-web/northstar-browser

    Configure, compile, and smoke-test a Meson-based C or C++ desktop browser on Linux, macOS, or Windows, and diagnose dependency, compiler, linker, runtime-library, build-directory, or…

    127 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Diagnose Rendering Regressions

    nordstjernen-web/northstar-browser

    Diagnose and fix visual, geometry, hit-testing, and viewport regressions in a browser rendering engine.

    127 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Fix Web Platform Compat

    nordstjernen-web/northstar-browser

    Diagnose and fix standards-compatibility gaps in a browser engine across HTML, DOM, JavaScript bindings, events, CSSOM, forms, fetch, storage, and Web APIs.

    127 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Port Engine Changes

What does Port Engine Changes do?

Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction. Port Engine Changes is an agent skill from nordstjernen-web/northstar-browser. Port a browser-engine change between sibling editions or long-lived branches of the same codebase, in either direction.

When should I use Port Engine Changes?

Port Engine Changes fits situations like: cherry-picks where the two trees share most engine sources but differ in features; vendored dependencies.

How do I install Port Engine Changes in Claude Code?

Run `npx skills add nordstjernen-web/northstar-browser --skill port-engine-changes -a claude-code`. Or copy the skill folder (.agents/skills/port-engine-changes in nordstjernen-web/northstar-browser) into .claude/skills/port-engine-changes in your project. Claude Code loads it when a task matches its description.

How do I install Port Engine Changes in Codex?

Run `npx skills add nordstjernen-web/northstar-browser --skill port-engine-changes -a codex`. Or copy the skill folder (.agents/skills/port-engine-changes in nordstjernen-web/northstar-browser) into .agents/skills/port-engine-changes in your project. Codex loads it when a task matches its description.

Can I use Port Engine Changes 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 nordstjernen-web/northstar-browser --skill port-engine-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/port-engine-changes, .gemini/skills/port-engine-changes, .github/skills/port-engine-changes and .opencode/skills/port-engine-changes in your project.

What does Port Engine Changes need to run?

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

Does Port Engine Changes access the network?

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

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

Port Engine Changes is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Port Engine Changes use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Port Engine Changes?

Skills that share tags, products or a category with Port Engine Changes: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Port Engine Changes?

nordstjernen-web (a GitHub organization) maintains it in nordstjernen-web/northstar-browser, which has 127 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.

Source: nordstjernen-web/northstar-browser on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.