Agent skill
jj-merge-repos
Merges two separate Jujutsu (jj) repositories into one. Use when combining repos, rebasing one repo onto another, or recovering from diverged histories.
Install this agent skill to your Project
npx add-skill https://github.com/edmundmiller/dotfiles/tree/main/.agents/skills/jj-merge-repos
SKILL.md
Merging JJ Repositories
Guide for merging two separate Jujutsu repositories into a single unified repo.
When to Use This Skill
- Combining two unrelated repositories into one
- Recovering from diverged histories (local vs remote rewrites)
- Splicing commit histories together
- Rebasing an entire repository onto another
How It Works
All JJ repos share a common empty root commit. When you add a remote from another repo and fetch, you get two diverging chains from that root. You can then:
- Delete one chain (if you just want the other repo's history)
- Rebase one chain onto the other (splice them together)
Quick Reference
Add and Fetch Another Repository
# Add the other repo as a remote
jj git remote add other-repo <url-or-path>
# Fetch all commits from it
jj git fetch --remote other-repo
View Both Histories
After fetching, you'll see two separate commit chains:
jj log
Both chains start from the shared empty root commit.
Option 1: Keep Only One History
Delete the unwanted chain of commits:
# Abandon all commits from the old/unwanted branch
jj abandon <commit-range>
Option 2: Splice Repositories Together
Rebase one repo's history onto the other:
# Move all commits from one chain atop the other
jj rebase --source <root-of-chain-to-move> --destination <tip-of-other-chain>
Example: Recovering from Diverged Histories
When local and remote diverged due to history rewriting:
# Add the remote (source of truth)
jj git remote add origin <url>
# Fetch remote commits
jj git fetch
# You now have two chains from root
# Delete the local chain you don't want
jj abandon <local-commits>
# Or rebase local work onto remote
jj rebase --source <local-root> --destination <remote-tip>
Example: Combining Two Unrelated Projects
# Start in repo A
cd repo-a
# Add repo B as a remote
jj git remote add repo-b /path/to/repo-b
# Fetch repo B's history
jj git fetch --remote repo-b
# Rebase repo B's commits onto repo A's main
jj rebase --source <repo-b-root> --destination main
Caveats
- Merge conflicts are likely when combining unrelated repos with overlapping files
- Resolve conflicts during the rebase as needed
- Consider whether you actually want the combined history or just the files
Tips
- Use
jj log --allto see all commits including from other remotes - The root commit (empty) is always shared between all chains
jj abandonremoves commits without affecting working copy- After cleanup, run
jj git pushto update remotes if needed
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
zbench
Benchmark interactive zsh performance with zsh-bench and track regressions. Use when benchmarking shell startup, comparing zsh latency after config changes, investigating slow shell, or running git bisect on performance. Trigger phrases: "benchmark zsh", "shell is slow", "zbench", "zsh-bench", "shell startup time", "profile zsh", "zsh performance".
nix-rebuild
Rebuild nix-darwin/NixOS system after dotfiles changes. Use when config files managed by Nix (lazygit, ghostty, etc.) need to be regenerated, or after editing any .nix file in the dotfiles repo.
hass-config-flow
Interact with Home Assistant via the REST API on a NixOS host. Use when adding integrations, querying entities, managing config flows, creating API tokens, or automating HA setup programmatically. Also covers identifying device protocols (Matter, Zigbee, Thread, HomeKit) from the device registry. Trigger phrases: "add HA integration", "configure home assistant", "query HA entities", "create HA token", "HA REST API", "pair homekit", "set up matter in HA", "add spotify to HA", "is this device zigbee or thread", "what protocol is this device", "move devices to ZHA", "identify matter devices".
hass-declarative
Manage Home Assistant automations, scenes, and scripts declaratively via NixOS modules. Covers adding/editing/removing entities in the domain-based Nix structure, the ensureEnabled wrapper (initial_state enforcement), the sweep service that cleans orphaned entities, entity identity (IDs, slugs, unique_ids), the eval test assertions, and the build-time manifest. Trigger phrases: "add HA automation", "new scene", "new script", "remove automation", "declarative HA", "sweep unmanaged", "entity drift", "ghost entity", "orphaned automation", "HA domain file", "eval-automations test", "hass assertion", "ensureEnabled", "initial_state".
agenix-secrets
Create, edit, and wire up agenix-encrypted secrets in this dotfiles repo. Use when adding API keys, tokens, credentials, passwords, or any sensitive values to NixOS host configs. Trigger phrases: "add a secret", "encrypt with agenix", "new age secret", "hide this value", "agenix secret".
linear
Read-only Linear issue access via the Linear GraphQL API.
Didn't find tool you were looking for?