How do I install the Yun Sync Repo skill?

Run npx skillmds@latest add matiinchauspe/yun-sync-repo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Yun Sync Repo skill do?

Bring an external repo into the workspace as work material — cloned into repos/ /, gitignored, with its own .git. It is listed under Coding & Dev Tools on SkillMD.

Is Yun Sync Repo safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Yun Sync Repo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Yun Sync Repo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Yun Sync Repo?

matiinchauspe (@matiinchauspe) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Yun Sync Repo by matiinchauspe — Agent Skill

Name: Yun Sync Repo
Author: matiinchauspe

File contents

yun-sync-repo

Brings an external repository into the workspace as work material. The repo is cloned into repos/<name>/, which is gitignored — the workspace versions only the harness, never the projects' code.

Preconditions

You MUST be at the workspace root (the directory containing AGENTS.md and skills/). Verify with the shell test [ -e AGENTS.md ] && [ -d skills ], never a lister piped to a matcher — given no path argument it prints nothing and still exits 0. If you are not at the root, STOP and tell the user to open their agent from the workspace root (see AGENTS.md rule 1). Do not clone from anywhere else.

Inputs

A git URL (https://…/repo.git, git@…:owner/repo.git), OR
A GitHub shorthand owner/repo, OR
An explicit <name> for the target folder (optional; defaults to the repo basename).

Steps

Resolve the target name. Use the explicit name if the user gave one; otherwise derive it from the URL basename without the .git suffix. Keep it kebab-case.
Check for collision. Look at repos/<name>/:
- If it already exists and is a clone of the same remote → do NOT re-clone. Report it is already synced, and offer git -C repos/<name> fetch --all --prune to update.
- If it exists but points to a different remote, or is a dirty non-repo directory → STOP and ask the user how to proceed. Never overwrite blindly.
Clone. git clone <url> repos/<name> — a full clone (worktrees need full history; do NOT use --depth). Expand a GitHub shorthand first — owner/repo → https://github.com/owner/repo.git — or git clone reads it as a local path.
Verify the clone.
- git -C repos/<name> rev-parse --is-inside-work-tree returns true.
- git -C repos/<name> remote -v shows the expected remote.
Confirm isolation. repos/ is gitignored at the workspace level, so git status at the workspace root must NOT list the new repo. If it does, the workspace .gitignore is broken — fix it before continuing.
Report. Give the ready path repos/<name>/ and its default branch.

Notes

Never clone into the workspace root or into skills/. Only into repos/<name>/.
Do NOT cd into repos/<name>/ to keep working — stay at the workspace root so the harness stays loaded (AGENTS.md rule 1). Operate on the repo via git -C repos/<name>, or spawn an isolated worktree with yun-spawn-worktree.

---name: yun-sync-repodescription: Bring an external repo into the workspace as work material — cloned into repos/<name>/, gitignored, with its own .git.---# yun-sync-repoBrings an external repository into the workspace as work material. The repo is clonedinto `repos/<name>/`, which is gitignored — the workspace versions only the harness,never the projects' code.## Preconditions- You MUST be at the workspace root (the directory containing `AGENTS.md` and `skills/`). Verify with the shell test `[ -e AGENTS.md ] && [ -d skills ]`, never a lister piped to a matcher — given no path argument it prints nothing and still exits 0. If you are not at the root, STOP and tell the user to open their agent from the workspace root (see AGENTS.md rule 1). Do not clone from anywhere else.## Inputs- A git URL (`https://…/repo.git`, `git@…:owner/repo.git`), OR- A GitHub shorthand `owner/repo`, OR- An explicit `<name>` for the target folder (optional; defaults to the repo basename).## Steps1. **Resolve the target name.** Use the explicit name if the user gave one; otherwise derive it from the URL basename without the `.git` suffix. Keep it kebab-case.2. **Check for collision.** Look at `repos/<name>/`: - If it already exists and is a clone of the same remote → do NOT re-clone. Report it is already synced, and offer `git -C repos/<name> fetch --all --prune` to update. - If it exists but points to a different remote, or is a dirty non-repo directory → STOP and ask the user how to proceed. Never overwrite blindly.3. **Clone.** `git clone <url> repos/<name>` — a full clone (worktrees need full history; do NOT use `--depth`). Expand a GitHub shorthand first — `owner/repo` → `https://github.com/owner/repo.git` — or `git clone` reads it as a local path.4. **Verify the clone.** - `git -C repos/<name> rev-parse --is-inside-work-tree` returns `true`. - `git -C repos/<name> remote -v` shows the expected remote.5. **Confirm isolation.** `repos/` is gitignored at the workspace level, so `git status` at the workspace root must NOT list the new repo. If it does, the workspace `.gitignore` is broken — fix it before continuing.6. **Report.** Give the ready path `repos/<name>/` and its default branch.## Notes- Never clone into the workspace root or into `skills/`. Only into `repos/<name>/`.- Do NOT `cd` into `repos/<name>/` to keep working — stay at the workspace root so the harness stays loaded (AGENTS.md rule 1). Operate on the repo via `git -C repos/<name>`, or spawn an isolated worktree with `yun-spawn-worktree`.

Frequently asked questions

Yun Sync Repo