How do I install the Sync Dev skill?

Run npx skillmds@latest add tomevault-io/sync-dev 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.

Is Sync Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sync Dev?

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 Sync Dev free to use?

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

Who published Sync Dev?

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

Sync Dev by tomevault-io — Agent Skill

Name: Sync Dev
Author: tomevault-io

Sync Dev

Use this skill when the user wants to update the local dev branch to match origin/dev — fetch latest remote refs and fast-forward. Triggers include phrases like "sync dev", "update dev", "pull dev", "dev ブランチを最新に", "dev を更新", "リモートに追従". Performs switch to dev, fetch origin --prune, then merge --ff-only origin/dev. Notifies the user if fast-forward is not possible instead of attempting a non-FF merge.

tomevault-io Updated Sep 17, 2026

File contents

sync-dev

Bring the local dev branch up to date with origin/dev. Only fast-forward updates are performed; anything else stops and reports to the user.

When to use

Invoke this skill when the user expresses any of the following intents:

"Sync dev", "update dev", "pull dev", "dev ブランチを最新にして", "dev を更新して"
Wanting the local development branch to catch up with the remote
Refreshing the base before starting new work

Procedure

Run the steps below in order using the Bash tool. Proceed to the next step only if the previous one succeeds.

Step 1: Check working-tree state

Verify there are no uncommitted changes.

git status --porcelain

If the output is non-empty (working tree is dirty), stop and report the situation to the user. Do not stash or discard changes on your own.

Step 2: Switch to dev

git switch dev

This succeeds even when already on dev. If it fails (e.g. the dev branch does not exist), stop and notify the user.

Step 3: Fetch from origin

git fetch origin --prune

--prune cleans up references to remote branches that have been deleted upstream.

Step 4: Fast-forward merge

git merge --ff-only origin/dev

On success: report concisely how many commits were pulled in, or that the branch was already up to date.
On failure (fast-forward not possible): do not attempt a non-FF merge, rebase, or reset. Stop and tell the user:
- Fast-forward was not possible
- Local dev has likely diverged from the remote
- Suggest inspecting the situation with e.g. git log --oneline --graph --decorate dev origin/dev
- Leave the resolution choice (rebase / merge / reset) to the user

Notes

This skill performs read-only and fast-forward operations only. It never uses force flags or reset --hard.
Whenever the working tree is dirty or a fast-forward is not possible, defer to the user — never resolve it automatically.
Keep the final report short (one or two sentences): how many commits advanced, or "Already up to date."

Source: fetus-hina/stat.ink — distributed by TomeVault.

---name: sync-devdescription: Use this skill when the user wants to update the local dev branch to match origin/dev — fetch latest remote refs and fast-forward. Triggers include phrases like "sync dev", "update dev", "pull dev", "dev ブランチを最新に", "dev を更新", "リモートに追従". Performs switch to dev, fetch origin --prune, then merge --ff-only origin/dev. Notifies the user if fast-forward is not possible instead of attempting a non-FF merge.---# sync-devBring the local `dev` branch up to date with `origin/dev`. Only fast-forward updates are performed; anything else stops and reports to the user.## When to useInvoke this skill when the user expresses any of the following intents:- "Sync dev", "update dev", "pull dev", "dev ブランチを最新にして", "dev を更新して"- Wanting the local development branch to catch up with the remote- Refreshing the base before starting new work## ProcedureRun the steps below in order using the Bash tool. Proceed to the next step only if the previous one succeeds.### Step 1: Check working-tree stateVerify there are no uncommitted changes.```bashgit status --porcelain```If the output is non-empty (working tree is dirty), stop and report the situation to the user. Do **not** stash or discard changes on your own.### Step 2: Switch to dev```bashgit switch dev```This succeeds even when already on `dev`. If it fails (e.g. the `dev` branch does not exist), stop and notify the user.### Step 3: Fetch from origin```bashgit fetch origin --prune````--prune` cleans up references to remote branches that have been deleted upstream.### Step 4: Fast-forward merge```bashgit merge --ff-only origin/dev```- **On success**: report concisely how many commits were pulled in, or that the branch was already up to date.- **On failure (fast-forward not possible)**: do **not** attempt a non-FF merge, rebase, or reset. Stop and tell the user: - Fast-forward was not possible - Local `dev` has likely diverged from the remote - Suggest inspecting the situation with e.g. `git log --oneline --graph --decorate dev origin/dev` - Leave the resolution choice (rebase / merge / reset) to the user## Notes- This skill performs **read-only and fast-forward operations only**. It never uses force flags or `reset --hard`.- Whenever the working tree is dirty or a fast-forward is not possible, defer to the user — never resolve it automatically.- Keep the final report short (one or two sentences): how many commits advanced, or "Already up to date."---> Source: [fetus-hina/stat.ink](https://github.com/fetus-hina/stat.ink) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions