Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .claude/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add yamcodes/arkenv --skill sync-main -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .agents/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add yamcodes/arkenv --skill sync-main -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .cursor/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add yamcodes/arkenv --skill sync-main -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .gemini/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install yamcodes/arkenv sync-main
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add yamcodes/arkenv --skill sync-main -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .github/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add yamcodes/arkenv --skill sync-main -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "sync-main" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/sync-main into .opencode/skills/sync-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-main", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
sync-main
GitHub stars
145
Token cost
~1.4k tokens
SKILL.md length
678 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT
At a glance
Update the v0 docs archive on main (arkenv-v0.vercel.app) immediately without waiting for a new npm release.
Works in 3 steps: Doc-Only (Easy Case): All changed files… → Infra-Only (Easy Case + Force): There… → Code Changes (Hard Case): There are…
The user mentions hotfix docs
SKILL.md covers Analysis Step (Do This First), Easy Case Workflows and Hard Case Workflow
Calls git, gh and pnpm; reaches arkenv-v0.vercel.app
What it does
Sync Main is an agent skill from yamcodes/arkenv. Update the v0 docs archive on main (arkenv-v0.vercel.app) immediately without waiting for a new npm release. Use this skill whenever the user mentions 'hotfix docs', 'push doc changes live now', 'promote docs to main', 'bypass package release for docs', 'sync-main', 'sync main', or wants to rescue already-merged doc commits from dev. It handles cherry-picking to main and merging main back into dev to prevent git drift. Note: Production / arkenv.js.org tracks v1 — sync-main does not flip apex.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow. It works with Git, Vercel, npm and GitHub. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.
When your agent uses it
The user mentions hotfix docs
Push doc changes live now
Promote docs to main
Bypass package release for docs
Example prompts
“hotfix docs”
“push doc changes live now”
“promote docs to main”
“/sync-main”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
1Doc-Only (Easy Case): All changed files are strictly under docs/, apps/www/, or are root-level Markdown files (matching the regex…
2Infra-Only (Easy Case + Force): There are no changes to package code, tests, or examples, but there are changes to workflows, scripts, or…
3Code Changes (Hard Case): There are modifications to files in the packages/, tests/, examples/, or apps/ directories (unreleased library…
What it can do on your machine
Read from SKILL.md and the folder at commit 74b3732. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
gh
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
arkenv-v0.vercel.app
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sync Main loads about 1.4k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 678 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~127
When it runs· the whole SKILL.md, loaded when a task matches
~1.4k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/sync-main/SKILL.md (or your agent's skills folder).
name
sync-main
description
Update the v0 docs archive on main (arkenv-v0.vercel.app) immediately without waiting for a new npm release. Use this skill whenever the user mentions 'hotfix docs', 'push doc changes live now', 'promote docs to main', 'bypass package release for docs', 'sync-main', 'sync main', or wants to rescue already-merged doc commits from dev. It handles cherry-picking to main and merging main back into dev to prevent git drift. Note: Production / arkenv.js.org tracks v1 — sync-main does not flip apex.
metadata
internal: true
Sync Main
This skill enables you to safely sync documentation and tooling changes from the dev branch to main without waiting for the next package release, while ensuring that the dev and main branches remain in a clean, compatible topological state (preventing future merge conflicts).
After the RC docs cutover (Option A), a push to main refreshes the v0 archive at https://arkenv-v0.vercel.app. It does not deploy Production / arkenv.js.org (that tracks v1). Use this skill for urgent legacy v0 doc fixes, not for the live v1 site.
Analysis Step (Do This First)
Before performing any Git actions, you must analyze the changes between dev and main to classify the sync:
Run the following command to check the list of changed files:
Based on the file list, classify the sync into one of the following three categories:
Doc-Only (Easy Case): All changed files are strictly under docs/, apps/www/, or are root-level Markdown files (matching the regex ^(docs/|apps/www/|[^/]+\.md)$).
Infra-Only (Easy Case + Force): There are no changes to package code, tests, or examples, but there are changes to workflows, scripts, or skills (e.g. .github/workflows/, scripts/, skills/).
Code Changes (Hard Case): There are modifications to files in the packages/, tests/, examples/, or apps/ directories (unreleased library features, fixes, or test/example updates).
Easy Case Workflows
Category 1: Doc-Only Sync
Since the changes are strictly doc-only, they are safe to sync directly:
Instruct the user that they can run the Sync main workflow normally.
Or trigger it automatically via GitHub CLI:bash
gh workflow run sync-main.yml --ref dev
Category 2: Infra-Only Sync
Since the changes contain tooling or workflow updates but do not touch the library package code, they can be synced, but the workflow's safety check will block them unless overridden:
Instruct the user that they can run the Sync main workflow but must check the force_override checkbox in the GitHub UI.
Or trigger it automatically via GitHub CLI with the bypass flag:bash
gh workflow run sync-main.yml --ref dev -f force_override=true
Hard Case Workflow
If there are changes in the packages/ directory, do not execute any git commands automatically. You must stop and interview the user in the chat to align on how to proceed.
Show full SKILL.md (339 more words)Show less
The Interview
Present the user with a clear summary of the unreleased package files that were detected, outline their choices, and make a recommendation based on the situation:
Option 1: Wait for Release
Keep the doc changes on dev and let them deploy naturally on the next package release.
Recommendation: Use this if the doc fix is not urgent.
Option 2: Run a Patch Release
Release a patch version of the packages (pnpm changeset -> trigger release workflow).
Recommendation: Use this if the doc fix is urgent, and the unreleased library code on dev is stable and ready to go live.
Option 3: Cherry-Pick/Rescue
Cherry-pick only the doc commits onto main (if the doc fixes are isolated in their own clean commits).
Recommendation: Use this if the doc fix is urgent, the library code on dev cannot be released, AND the doc commits do not contain unreleased code.
Option 4: Manual Recreation (Tangled Commits)
If the urgent doc fix is bundled in the exact same commit as unreleased package code, do not cherry-pick. Instead, manually recreate the doc fix directly against main using your code editing tools.
Recommendation: Use this if the doc fix is urgent but the commits are hopelessly tangled with unreleased code.
Executing Option 3 (Cherry-Pick / Rescue)
If the user explicitly approves Option 3, follow these steps using the helper script:
Identify Commit Hashes:
Locate the specific commit hashes on dev containing the doc changes.
Run Rescue Script:
Execute the helper script to cherry-pick these commits onto a branch from origin/main:bash
Sync Main next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…
Update the v0 docs archive on main (arkenv-v0.vercel.app) immediately without waiting for a new npm release. Sync Main is an agent skill from yamcodes/arkenv.app) immediately without waiting for a new npm release.
When should I use Sync Main?
Sync Main fits situations like: the user mentions hotfix docs; push doc changes live now; promote docs to main; bypass package release for docs.
How do I install Sync Main in Claude Code?
Run `npx skills add yamcodes/arkenv --skill sync-main -a claude-code`. Or copy the skill folder (skills/sync-main in yamcodes/arkenv) into .claude/skills/sync-main in your project. Claude Code loads it when a task matches its description.
How do I install Sync Main in Codex?
Run `npx skills add yamcodes/arkenv --skill sync-main -a codex`. Or copy the skill folder (skills/sync-main in yamcodes/arkenv) into .agents/skills/sync-main in your project. Codex loads it when a task matches its description.
Can I use Sync Main in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yamcodes/arkenv --skill sync-main -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-main, .gemini/skills/sync-main, .github/skills/sync-main and .opencode/skills/sync-main in your project.
What does Sync Main need to run?
Going by SKILL.md and its folder, Sync Main needs the command-line tools its instructions call (git, gh and pnpm).
Does Sync Main access the network?
SKILL.md names 1 domain. In commands or code: arkenv-v0.vercel.app; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Sync Main safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sync Main use?
Sync Main is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sync Main use?
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sync Main?
Skills that share tags, products or a category with Sync Main: Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars) and npm Package Publisher (klaudworks/universal-skills, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sync Main?
yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.
Source: yamcodes/arkenv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
