What is docs-website-update?

A guide for updating the Nx project's documentation website, including its live and release branches. Nx is a tool for managing related applications and libraries in one code repository.

Use it in the Nx repository to find the correct website and release branches and copy documentation commits to both.

It helps keep documentation changes on both branches needed for the current website and future patch releases.

docs-website-update — Skill by nrwl

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/nrwl/nx/docs-website-update

Any agent

npx skills add nrwl/nx --skill docs-website-update

Clone the repo

git clone --depth 1 https://github.com/nrwl/nx

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,111 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01111
Opus 5	$0.00000	$0.00556
Sonnet 5	$0.00000	$0.00222
Haiku 4.5	$0.00000	$0.00111

Measured 2d ago against content hash 56eaadc475f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-website-update scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/docs-website-update/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

git fetch 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/...).
```
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.
```
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.

Report both branch names before doing any work.

2. Sync the branches

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)

On <website-branch>, get the last commit subject -> /tmp/last-website-commit.txt
Back on master, find the commit whose subject matches /tmp/last-website-commit.txt -> sha in /tmp/last-master-sha.txt
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)

Read the full file on GitHub · 104 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 104 lines · 133 tokens per session scan A 56eaadc475f9

Subscribe to this mod's changes

docs-website-update is a skill published in the GitHub repository nrwl/nx (29,291 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,111 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Writing and docs angular build build-system build-tool building-tool cli

turborepo

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines…

vercel/turborepo · 111 tokens

debug-task

Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…

moonrepo/moon · 231 tokens

improve-code-quality

Analyze and improve code quality for any path in the monorepo. Use whenever the user asks to improve, audit, review, clean up, refactor, lint, or check code quality for a directory or file. Also trigger for requests about security review, performance optimization, robustness checks, dependency audits, or readability…

moonrepo/moon · 116 tokens

zuke-write-build

Write or edit a Zuke build (zuke.ts) — the code-first, strongly-typed build system for Deno/TypeScript. Use when adding or changing targets, wiring dependencies, calling a tool wrapper (DenoTasks, NpmTasks, DockerTasks, ...), generating CI, or authoring/refactoring a zuke.ts build file. For first-time project…

zuke-build/zuke · 93 tokens

zuke-setup

Set up Zuke — a code-first, strongly-typed build automation system for Deno/TypeScript — in a project. Use when the user wants to add Zuke to a repo, scaffold a zuke.ts build file, install the Zuke CLI, or bootstrap the ./zuke launcher. After scaffolding, switch to the zuke-write-build skill to author targets.

zuke-build/zuke · 82 tokens

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.…

moonrepo/moon · 77 tokens