.agents/skills/jj-merge-repos/SKILL.md
Merges two separate Jujutsu (jj) repositories into one. Use when combining repos, rebasing one repo onto another, or recovering from diverged histories.
npx skillsauth add edmundmiller/dotfiles jj-merge-reposInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide for merging two separate Jujutsu repositories into a single unified repo.
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:
# 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
After fetching, you'll see two separate commit chains:
jj log
Both chains start from the shared empty root commit.
Delete the unwanted chain of commits:
# Abandon all commits from the old/unwanted branch
jj abandon <commit-range>
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>
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>
# 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
jj log --all to see all commits including from other remotesjj abandon removes commits without affecting working copyjj git push to update remotes if neededdevelopment
Read-only Linear issue access via the Linear GraphQL API.
data-ai
## <!-- Purpose: Teach agents fast day-to-day memory browse/search/read/sync workflows in pi-context-repo. --> name: searching-memory description: > Search, browse, and inspect memory quickly in pi-context-repo. Use when asked to find prior notes, inspect memory files, locate preferences, or sync recent memory updates. Trigger phrases: "search memory", "list memory files", "find in memory", "read memory file", "memory status", "sync memory". --- # Searching Memory Use this workflow for fast
development
Comprehensive guide for initializing or reorganizing agent memory into a deeply hierarchical file structure. Use when running /init, when user asks to set up memory, or when memory needs a major reorganization. Trigger phrases: "initialize memory", "set up memory", "populate memory", "build my memory", "memory init".
data-ai
Decomposes and reorganizes agent memory files into focused, single-purpose components. Use when memory has large multi-topic blocks, redundancy, or poor organization. Trigger phrases: "defrag memory", "reorganize memory", "clean up memory files", "split memory blocks".