Agent skill

Docs Website Update

by nrwl in nrwl/nx

Sync docs commits from master out to the live docs branches in the nx repo: cherry-picks docs( / feat(nx-dev) commits onto website-<major AND the latest <major.<minor.x release branch.

MITAuto-check passed

Install Docs Website Update

skills CLI
$ npx skills add nrwl/nx --skill docs-website-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nrwl/nx docs-website-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nrwl/nx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/docs-website-update .claude/skills/docs-website-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
docs-website-update
GitHub stars
29k
Token cost
~1.2k tokens
SKILL.md length
431 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Sync docs commits from master out to the live docs branches in the nx repo: cherry-picks docs( / feat(nx-dev) commits onto website-<major AND the latest <major.<minor.x release branch.

  • Works in 6 steps: Determine the branches → Sync the branches → Build the cherry-pick list (from the… → …
  • Update the docs branch
  • SKILL.md covers Why two branches and How to Update
  • Calls git

What it does

Docs Website Update is an agent skill from nrwl/nx. Sync docs commits from master out to the live docs branches in the nx repo: cherry-picks docs( / feat(nx-dev) commits onto website-<major AND the latest <major.<minor.x release branch. Use when "update the docs branch", "update nx.dev", "push the latest docs changes out", "cherry-pick docs commits", "sync website-23", "ship docs to the website branch", "update the docs website", "get docs onto the release branch", or any request to move already-merged docs commits from master onto the branches that deploy them.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The Monorepo Platform that amplifies both developers and AI agents. Nx optimizes your builds, scales your CI, and fixes failed PRs automatically. Ship in half the time. The licence is MIT.

When your agent uses it

  • Update the docs branch
  • Push the latest docs changes out
  • Cherry-pick docs commits
  • Sync website-23

Example prompts

  • “update the docs branch”
  • “update nx.dev”
  • “push the latest docs changes out”
  • “/docs-website-update”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git *), Read, Write

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Determine the branches
  2. Sync the branches
  3. Build the cherry-pick list (from the website branch)
  4. Cherry-pick onto the website branch
  5. Cherry-pick the SAME list onto the release branch
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit f214056. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git *)
    • Read
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Docs Website Update loads about 1.2k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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.

SKILL.md

The full file from nrwl/nx at commit f214056, republished under its MIT licence (© nrwl). 431 words, ~1,200 tokens.

Download SKILL.mdSave it as .claude/skills/docs-website-update/SKILL.md (or your agent's skills folder).
name
docs-website-update
description
Sync docs commits from `master` out to the live docs branches in the nx repo: cherry-picks `docs(` / `feat(nx-dev)` commits onto `website-<major>` AND the latest `<major>.<minor>.x` release branch. Use when "update the docs branch", "update nx.dev", "push the latest docs changes out", "cherry-pick docs commits", "sync website-23", "ship docs to the website branch", "update the docs website", "get docs onto the release branch", or any request to move already-merged docs commits from master onto the branches that deploy them.
allowed-tools
Bash(git *), Read, Write

Update Docs Website

This skill works in the nx repo only.

CRITICAL:

  • If you are not in the nx repo, say so and stop working!
  • If there are uncommitted/untracked files, say so and stop working!

Why two branches

Docs commits must land on BOTH:

  • website-<major> (e.g. website-23) - deploys nx.dev for the current major
  • the latest release branch <major>.<minor>.x (e.g. 23.1.x) - used for patch releases, and the release pipeline overwrites the website-<major> branch from it

If only website-23 gets the commit, the next patch release from 23.1.x wipes it.

How to Update

1. Determine the branches

The + on each refspec is required. A release force-pushes website-<major> from the release branch, so a non-forced fetch is rejected as non-fast-forward and leaves origin/website-<major> pointing at the pre-release commit.

bash
git fetch origin '+refs/heads/master:refs/remotes/origin/master'
git fetch origin '+refs/heads/website-*:refs/remotes/origin/website-*'
git fetch origin '+refs/heads/*.x:refs/remotes/origin/*.x'
  • Website branch: highest origin/website-<N> where <N> is an integer. Exclude website-master and any branch with extra path segments (e.g. website-19-cherry-01/...).
    bash
    git for-each-ref --format='%(refname:short)' 'refs/remotes/origin/website-*' \
      | grep -E '^origin/website-[0-9]+$' | sort -V | tail -1
  • Release branch: highest origin/<N>.<minor>.x with the SAME major <N> as the website branch.
    bash
    git for-each-ref --format='%(refname:short)' 'refs/remotes/origin/*.x' \
      | grep -E "^origin/${MAJOR}\.[0-9]+\.x$" | sort -V | tail -1
    If no release branch exists for that major, say so and continue with the website branch only.

Confirm the remote-tracking refs actually match the remote before touching them:

bash
git ls-remote origin refs/heads/<website-branch> refs/heads/<release-branch>
git rev-parse origin/<website-branch> origin/<release-branch>

If the shas differ, the fetch did not take - stop and re-fetch. Every later step (the anchor commit, the cherry-pick list, any conflict) is wrong otherwise.

Report both branch names before doing any work.

2. Sync the branches
bash
git checkout master && git reset --hard origin/master
git checkout <website-branch> && git reset --hard origin/<website-branch>
git checkout <release-branch> && git reset --hard origin/<release-branch>
3. Build the cherry-pick list (from the website branch)
  1. On <website-branch>, get the last commit subject -> /tmp/last-website-commit.txt
  2. Back on master, find the commit whose subject matches /tmp/last-website-commit.txt -> sha in /tmp/last-master-sha.txt
  3. On master, list commits between that sha and HEAD, filtered to subjects starting with docs( or feat(nx-dev) -> /tmp/commits-to-cherry-pick.txt (oldest at bottom, as git log prints it)
Show full SKILL.md (156 more words)Show less
4. Cherry-pick onto the website branch

On <website-branch>, oldest to newest:

bash
git cherry-pick <sha>
  • On failure: record in /tmp/failed-website.txt, git cherry-pick --abort, move on.
  • If the pick is empty (already applied): git cherry-pick --skip, record as skipped.
5. Cherry-pick the SAME list onto the release branch

The release branch was cut from master at a different point, so some commits may already be there.

  1. Skip any commit whose subject already appears in the release branch's log:
    bash
    git log <release-branch> --format='%s' | grep -Fxq "<subject>"
  2. Cherry-pick the rest oldest to newest, same rules as step 4.
    • Failures -> /tmp/failed-release.txt
    • Empty picks -> git cherry-pick --skip

Conflicts are more likely here than on the website branch - do NOT try to resolve them, just abort and report.

6. Report

Print a per-branch breakdown:

BranchCherry-pickedAlready present / skippedFailed

List failed shas with subjects so they can be handled manually.

Do NOT push. End by reminding which branches have unpushed commits, e.g.:

git push origin website-23
git push origin 23.1.x

© nrwl, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/docs-website-update of nrwl/nx.

Open the folder on GitHubat commit f214056

Compare with similar skills

Docs Website Update 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.

Docs Website Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Website Update this skillnrwl/nx29k—~1.2kAutomated safety check: PassMIT
Commitsickn33/agentic-awesome-skills47k2 repos~1.3kAutomated safety check: PassMIT
Commitdavila7/claude-code-templates32k3 repos~730Automated safety check: PassMIT
Commitwindmill-labs/windmill18k—~447Automated safety check: PassCustom licence
Commitccusage/ccusage19k—~722Automated safety check: PassCustom licence
CommitsJetBrains/intellij-community21k—~589Automated safety check: PassCustom licence

Similar skills

  • Commit

    sickn33/agentic-awesome-skills

    ALWAYS use this skill when committing code changes — never commit directly without it.

    47k GitHub starsUsed in 2 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Commit

    davila7/claude-code-templates

    Create commit messages following Sentry conventions. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 3 repos~730 tokens
    DevelopmentAuto-check passed
  • Commit

    windmill-labs/windmill

    Create a git commit with conventional commit format. An agent skill from windmill-labs/windmill.

    18k GitHub stars~447 tokensUpdated today
    DevelopmentAuto-check passed
  • Commit

    ccusage/ccusage

    Creates atomic Conventional Commits. An agent skill from ccusage/ccusage.

    19k GitHub stars~722 tokensUpdated today
    DevelopmentAuto-check passed
  • Commits

    JetBrains/intellij-community

    Official

    Create, amend, or rename IntelliJ commits and write commit messages.

    21k GitHub stars~589 tokensUpdated today
    DevelopmentAuto-check passed
  • Commit

    antiwork/gumroad

    Stage and commit changes with a clear, concise commit message.

    9.8k GitHub stars~503 tokensUpdated today
    DevelopmentAuto-check passed
  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    Auto-check passed
  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 6 repos~3.5k tokens
    Auto-check passed
  • Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    Auto-check: notes
  • Author or scope a first-party Nx migration. An agent skill from nrwl/nx.

    29k GitHub stars~12k tokensUpdated today
    Auto-check: notes
  • Generate code using nx generators. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Check modified Nx documentation pages against the astro-docs style guide.

    29k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about Docs Website Update

What does Docs Website Update do?

Sync docs commits from master out to the live docs branches in the nx repo: cherry-picks docs( / feat(nx-dev) commits onto website-<major AND the latest <major.<minor.x release branch. Docs Website Update is an agent skill from nrwl/nx.x release branch.

When should I use Docs Website Update?

Docs Website Update fits situations like: update the docs branch; push the latest docs changes out; cherry-pick docs commits; sync website-23.

How do I install Docs Website Update in Claude Code?

Run `npx skills add nrwl/nx --skill docs-website-update -a claude-code`. Or copy the skill folder (.claude/skills/docs-website-update in nrwl/nx) into .claude/skills/docs-website-update in your project. Claude Code loads it when a task matches its description.

How do I install Docs Website Update in Codex?

Run `npx skills add nrwl/nx --skill docs-website-update -a codex`. Or copy the skill folder (.claude/skills/docs-website-update in nrwl/nx) into .agents/skills/docs-website-update in your project. Codex loads it when a task matches its description.

Can I use Docs Website Update 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 nrwl/nx --skill docs-website-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-website-update, .gemini/skills/docs-website-update, .github/skills/docs-website-update and .opencode/skills/docs-website-update in your project.

What does Docs Website Update need to run?

Going by SKILL.md and its folder, Docs Website Update needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash(git *), Read, Write.

Does Docs Website Update access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Docs Website Update 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 Docs Website Update use?

Docs Website Update 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 Docs Website Update use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Docs Website Update?

Skills that share tags, products or a category with Docs Website Update: Commit (sickn33/agentic-awesome-skills, 47k stars), Commit (davila7/claude-code-templates, 32k stars), Commit (windmill-labs/windmill, 18k stars) and Commit (ccusage/ccusage, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Website Update?

nrwl (a GitHub organization) maintains it in nrwl/nx, which has 29,394 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: nrwl/nx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.