Synchronize git worktrees with the Paseo workspace registry and reap merged work.
npx skills add https://github.com/mimukit/skills --skill paseokit-mimukit
Please help me install this Agent Skill. Skill: paseokit Source: https://github.com/mimukit/skills/tree/main/skills/paseokit Command: npx skills add https://github.com/mimukit/skills --skill paseokit-mimukit
git worktree never appear in the Paseo sidebar, and finished work leaves dead registry rows and orphaned directories behind. This Skill reconciles that drift in both directions, registering missing worktrees and cleaning up duplicates, tombstones, and merged work. ## Core Features & Use Cases - Drift detection (list): Joins git worktree list, paseo workspace ls, and Paseo state files to give every row a verdict such as unregistered, duplicate, orphaned, tombstoned, or reapable. - Registry sync (sync): Registers unregistered worktrees with the correct project id, retitles auto-generated rows from issue data, and restores tombstoned workspaces on confirmation, without ever archiving or touching disk. - Safe cleanup (clean): Collapses duplicate rows, archives orphans, and tears down worktrees only after proving the pull request merged, the tree is clean, nothing is unpushed, and no live agent is attached, all behind one previewed confirmation. - Use Case: After merging several PRs, ask to clean up your Paseo workspaces; the Skill lists each merged worktree with its PR number, stops its agent sessions, removes the worktree through gitkit, deletes the local branch, and archives the registry row. ## Quick Start Ask the agent to sync my worktrees to Paseo so every git worktree in this project appears in the Paseo sidebar.High-intent search queries and answers about installing and using this skill.
Run the sync mode, which joins git worktree list with paseo workspace ls and registers each unregistered worktree via paseo workspace create --isolation local with the resolved project id. Project scope is the default; saying sync all widens it to every project on the machine.
Paseo registers nothing on its own, so a worktree created with plain git worktree stays invisible until something registers it. Run the list mode to see the drift verdicts, then sync to add the missing rows.
Yes, when the directory sits under a Paseo-owned hash path it runs git worktree remove --force after archiving the row, and a dirty tree is no protection. The clean mode therefore proves the pull request merged and the tree is clean before queuing any archive.
Yes, the clean mode finds worktrees whose PR merged, tree is clean, nothing is unpushed, and no live agent is attached. It previews every archive and delete in one table, then removes the worktree, deletes the branch, and archives the row after one confirmation.
Titles degrade to the branch name and the tracker column reads unknown, but list, sync, and align still work. The clean mode's teardown half stops entirely because only the tracker can prove a merge, while its registry reap still runs behind its own confirmation.
No, creating and removing worktrees stays with native git worktree under gitkit's convention. The Skill only manages Paseo registry rows, and its clean mode drives teardown through gitkit rather than letting a Paseo archive delete directories.
f4irlineCreate or reuse isolated git worktrees for target branches.
tkogutClose tracker issues that merged pull requests authoritatively fixed and comment on unresolved ones.
ai-wesAnalyze directory contents, detect duplicates, and organize files with confirmed moves.
getpaseoDiagnose Paseo setup, connectivity, provider, and update issues using current documentation.