Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Directs porting of widgets, dialogs, panels and transforms from PlotJuggler 3 to PlotJuggler 4 by lifting the original files intact and rebinding only the data paths.
Install PlotJuggler 3 to 4 Porting
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PlotJuggler/PlotJuggler pj3-port --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pj3-port .claude/skills/pj3-port && rm -rf skills-srcUse ~/.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/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .claude/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-portType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PlotJuggler/PlotJuggler pj3-port --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pj3-port .agents/skills/pj3-port && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .agents/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PlotJuggler/PlotJuggler pj3-port --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pj3-port .cursor/skills/pj3-port && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .cursor/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PlotJuggler/PlotJuggler.git --path .claude/skills/pj3-port--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PlotJuggler/PlotJuggler pj3-port --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pj3-port .gemini/skills/pj3-port && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .gemini/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PlotJuggler/PlotJuggler pj3-portInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pj3-port .github/skills/pj3-port && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .github/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PlotJuggler/PlotJuggler pj3-port --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PlotJuggler/PlotJuggler.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pj3-port .opencode/skills/pj3-port && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pj3-port" agent skill from https://github.com/PlotJuggler/PlotJuggler/tree/main-4.x/.claude/skills/pj3-port into .opencode/skills/pj3-port/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pj3-port", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pj3-port- GitHub stars
- 6.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 478 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Directs porting of widgets, dialogs, panels and transforms from PlotJuggler 3 to PlotJuggler 4 by lifting the original files intact and rebinding only the data paths.
- Porting a PJ3 widget, dialog or panel into PJ4
- SKILL.md covers Overview, Procedure, Done means and Red flags — stop and re-read…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Adding a UI element that PJ3 already has
What it does
The core strategy is a wholesale lift: copy the PJ3 files largely unchanged, then rebind only the data reads. The skill names the known failure mode as rewriting from scratch, improving things while porting, or renaming items users depend on, and sums it up as port, don't rewrite. The PJ3 source tree is read-only and must never be modified from PJ4.
The procedure starts by searching the PJ3 app and base folders for the feature and agreeing explicitly before building anything PJ3 lacks. It then creates a worktree, decides placement among the plotting, widgets, app and runtime packages using the root CLAUDE.md rules, and lifts the `.h`, `.cpp` and `.ui` files with only a short list of changes: naming and namespace style, an MPL-2.0 SPDX header, upgraded combo box and toggle widget classes, and byte-identical `.ui` object names. Data reads then move to the PJ4 datastore adapter and transform registry.
When your agent uses it
- Porting a PJ3 widget, dialog or panel into PJ4
- Adding a UI element that PJ3 already has
- Checking whether PJ3 has a feature before writing a new one
- Deciding which PJ4 package a ported file belongs in
Example prompts
- “Port the PJ3 curve list panel into PJ4 and rebind it to the new datastore.”
- “Does PlotJuggler 3 already have a zoom tracker? If so, port it instead of writing a new one.”
- “Where should the ported transform editor dialog live in the PJ4 packages?”
Requirements
- A local PlotJuggler 3 checkout to read from
- A PlotJuggler 4 repository worktree
What it can do on your machine
Read from SKILL.md and the folder at commit 346dee6. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
PlotJuggler 3 to 4 Porting loads about 1.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 478 words of instructions outside code blocks.
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 PlotJuggler/PlotJuggler at commit 346dee6, republished under its MPL-2.0 licence (© PlotJuggler). 478 words, ~1,077 tokens.
Download SKILL.mdSave it as
.claude/skills/pj3-port/SKILL.md (or your agent's skills folder).- name
- pj3-port
- description
- Use when porting any widget, dialog, panel, transform, or helper from PlotJuggler 3 into PJ4, when asked to add a UI element or feature that PJ3 already has, or when tempted to write a new one from scratch.
Porting from PlotJuggler 3
Overview
PJ4's core strategy is the wholesale lift (see pj_plotting/CLAUDE.md): port PJ3 files largely intact, then rebind only the data reads. The recorded failure mode is rewriting from scratch, "improving" while porting, or renaming things users depend on. Port, don't rewrite. Rebind, don't redesign.
PJ3 lives at ~/ws_plotjuggler/PlotJuggler/ — read-only, never modify it from PJ4.
Procedure
1. Locate the PJ3 source first. Before writing anything, search PJ3:
grep -ril "<feature keyword>" ~/ws_plotjuggler/PlotJuggler/plotjuggler_app/ \
~/ws_plotjuggler/PlotJuggler/plotjuggler_base/plotjuggler_app/— plot widgets, dockers, zoomers, tracker, drag-drop, dialogs, Lua UIplotjuggler_base/— shared base types (cross-check againstpj_basebefore porting; it may already exist)plotjuggler_plugins/— already ported; reference only
If PJ3 has it → port it. If PJ3 genuinely doesn't → say so explicitly and get agreement before greenfielding.
2. Worktree first. ./scripts/worktree-new.sh <branch> off origin/main before any edit (see the worktree skill).
3. Decide placement with root CLAUDE.md placement rules. Quick map: plot-family code → pj_plotting; reusable-by-any-Qt-app control → pj_widgets; app dialog / wiring → pj_app; service/state logic → pj_runtime. When the fit is ambiguous, ask — don't invent a location.
4. Lift the files. Copy .h/.cpp/.ui across, then apply only these transformations:
| Transform | Do | Don't |
|---|---|---|
| Style | PascalCase.{h,cpp}, PJ:: namespace, trailing_underscore_ members, clang-format | Restructure logic that already reads cleanly |
| License | Add // SPDX-License-Identifier: MPL-2.0 header | Copy PJ3 header boilerplate verbatim |
.ui widget classes | Upgrade QComboBox → PJ::ComboBox (via <customwidgets>); checkbox rows → QLabel + PJ::ToggleSwitch | — |
.ui objectNames | Preserve byte-identical (buttonLoadDatafile, displayTime, …) — layout files, QSS selectors, muscle memory depend on them | Rename anything, ever, without explicit approval |
| Comments | Keep PJ3's why-comments; delete narration | Add "ported from PJ3" / history comments |
5. Rebind the data paths — the only systematic rewrite.
| PJ3 | PJ4 |
|---|---|
PlotDataMapRef reads | DatastoreCurveAdapter over pj_datastore::DataReader |
TransformsMap | TransformRegistry (pj_runtime) |
| Direct main-window state | pj_runtime services: CatalogModel, SessionManager, PlaybackEngine |
| Widget↔widget time sync | IDataWidget::onTrackerTime(double) contract |
Keep PJ3's per-pixel behavior: no adapter-side decimation (Qwt's paint-time filtering owns that; pre-decimating breaks zoom).
Show full SKILL.md (185 more words)Show less
6. Preserve PJ3's performance guards. If the PJ3 code has a gate (e.g. use_opengl), port the gate; each one exists because the ungated path is measurably slower.
7. Tests. Add a gtest binary in the owning module's tests/ covering the rebound adapter/wiring (a factory-registration or wiring test protects against silent merge drops).
8. Improvements: flag, don't apply. Cleaner shape spotted while porting? List it with cost/benefit at the end and ask. Silently refactoring and silently skipping obvious wins are both violations.
Done means
- PJ3 source read; diff vs PJ3 is style + rebinding only (anything else called out)
-
.uiobjectNames byte-identical (verify:grep -o 'name="[^"]*"' old.ui new.ui | diff) - SPDX header on every new file; builds clean; module tests green
- Improvement list surfaced as questions, not commits
Red flags — stop and re-read this skill
- "The PJ3 code is old/ugly, cleaner to rewrite" — no; greenfield needs explicit agreement
- "I'll modernize the names while I'm here" — objectNames are frozen
- "This helper is small, faster to just write it" — search PJ3 first; it almost always exists
- "I improved X along the way" — should have been a question, not a change
© PlotJuggler, MPL-2.0. 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 .claude/skills/pj3-port of PlotJuggler/PlotJuggler.
Open the folder on GitHubat commit 346dee6
Compare with similar skills
PlotJuggler 3 to 4 Porting 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PlotJuggler 3 to 4 Porting this skillPlotJuggler/PlotJuggler | 6.2k | — | ~1.1k | Automated safety check: Pass | MPL-2.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 41k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| OBS Plugin Dependency Upgradesorayuki/obs-multi-rtmp | 5.1k | — | ~609 | Automated safety check: Pass | GPL-2.0 | |
| Ripwire Output Emissionredhat-et/ripwire | 2.4k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Skia Analystmono/SkiaSharp | 5.6k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Setup Devrelytcloud/pg_ducklake | 143 | — | ~2k | Automated safety check: Notes | MIT |
Similar skills
OBS Plugin Dependency Upgrade
sorayuki/obs-multi-rtmp
Updates the obs-multi-rtmp plugin repo to the latest upstream plugin template and OBS Studio version, including dependency metadata, then rebuilds it with CMake.
Ripwire Output Emission
redhat-et/ripwire
Rules for writing and converting formatted output in ripwire's C++ source with its emit helpers, keeping every printed byte identical to the old printf output.
Skia Analyst
mono/SkiaSharp
Analyze Skia features for SkiaSharp - produces a unified analysis of what shipped (upstream engine benefits, PR links, migration guides) and what's missing (impact/priority/effort scoring, hidden…
Setup Dev
relytcloud/pg_ducklake
Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.
- Official
ONNX Opset Bump Checklist
microsoft/onnxruntime
A checklist for upgrading the pinned ONNX version and opset in ONNX Runtime, covering the files to change, archive hashes, patch rebasing and release-candidate handling.
More from PlotJuggler/PlotJuggler
PlotJuggler 4 Perf Profiling
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
PlotJuggler Ship Check
PlotJuggler/PlotJuggler
Runs a gated finish-line checklist before committing a PlotJuggler PJ4 change: build proof, red-test triage, hooks, docs freshness and a diff self-review.
PlotJuggler Live Verification
PlotJuggler/PlotJuggler
Confirms that a change to PlotJuggler 4 really works in the running app by proving the rebuild, launching with real data and measuring the result.
Related
Works with
Categories
Questions about PlotJuggler 3 to 4 Porting
What does PlotJuggler 3 to 4 Porting do?
Directs porting of widgets, dialogs, panels and transforms from PlotJuggler 3 to PlotJuggler 4 by lifting the original files intact and rebinding only the data paths. The core strategy is a wholesale lift: copy the PJ3 files largely unchanged, then rebind only the data reads. The skill names the known failure mode as rewriting from scratch, improving things while porting, or renaming items users depend on, and sums it up as port, don't rewrite.
When should I use PlotJuggler 3 to 4 Porting?
PlotJuggler 3 to 4 Porting fits situations like: porting a PJ3 widget, dialog or panel into PJ4; adding a UI element that PJ3 already has; checking whether PJ3 has a feature before writing a new one; deciding which PJ4 package a ported file belongs in.
How do I install PlotJuggler 3 to 4 Porting in Claude Code?
Run `npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a claude-code`. Or copy the skill folder (.claude/skills/pj3-port in PlotJuggler/PlotJuggler) into .claude/skills/pj3-port in your project. Claude Code loads it when a task matches its description.
How do I install PlotJuggler 3 to 4 Porting in Codex?
Run `npx skills add PlotJuggler/PlotJuggler --skill pj3-port -a codex`. Or copy the skill folder (.claude/skills/pj3-port in PlotJuggler/PlotJuggler) into .agents/skills/pj3-port in your project. Codex loads it when a task matches its description.
Can I use PlotJuggler 3 to 4 Porting 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 PlotJuggler/PlotJuggler --skill pj3-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/pj3-port, .gemini/skills/pj3-port, .github/skills/pj3-port and .opencode/skills/pj3-port in your project.
What does PlotJuggler 3 to 4 Porting need to run?
SKILL.md names no scripts, command-line tools or credentials: PlotJuggler 3 to 4 Porting is instructions for the agent only. Our summary lists: A local PlotJuggler 3 checkout to read from; A PlotJuggler 4 repository worktree.
Does PlotJuggler 3 to 4 Porting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is PlotJuggler 3 to 4 Porting 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 PlotJuggler 3 to 4 Porting use?
PlotJuggler 3 to 4 Porting is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PlotJuggler 3 to 4 Porting 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 PlotJuggler 3 to 4 Porting?
Skills that share tags, products or a category with PlotJuggler 3 to 4 Porting: Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars), OBS Plugin Dependency Upgrade (sorayuki/obs-multi-rtmp, 5.1k stars), Ripwire Output Emission (redhat-et/ripwire, 2.4k stars) and Skia Analyst (mono/SkiaSharp, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PlotJuggler 3 to 4 Porting?
PlotJuggler (a GitHub organization) maintains it in PlotJuggler/PlotJuggler, which has 6,233 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 1, 2026.
Source: PlotJuggler/PlotJuggler on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.