Agent skill · Security

han-update-documentation

Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han re

testdoublegithub.com/testdoubleGitHub ↗
claude-codecan modify filesships scriptsMIT
Install
npx skills add testdouble/han --skill han-update-documentation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: yes
Allowed tools: ReadWriteEditGlobGrepAgentBash(git*)Bash(find*)
Path: .claude/skills/han-update-documentation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 154
Language: Shell

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Pre-requisites - git: !`which git 2>/dev/null || echo "not installed"` - repo root marker: !`find . -maxdepth 3 -name "plugin.json" -path "*/.claude-plugin/*" -type f` - skill roots: !`find . -maxdepth 2 -type d -name skills -path './han-*/skills' ! -path './han-plugin-builder/skills' 2>/dev/null | sed 's|^\./||' | sort` - agents directory: !`find . -maxdepth 2 -type d -name agents -path './han-*/agents' 2>/dev/null | sed 's|^\./||' | sort` **If any of the above are empty or read `not installed`:** this skill is intended to run inside the Han plugin repository. Tell the operator which marker is missing and stop. Do not attempt to operate on a different repo. ## Project Context - current branch: !`git branch --show-current 2>/dev/null || echo unknown` - default branch: !`git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknown` ## Step 1: Detect mode and scope Run `${CLAUDE_SKILL_DIR}/scripts/detect-doc-update-context.sh` and read its output. Branch on the `mode:` line. The script also emits the **skill roots** (between `skill-roots-start` and `skill-roots-end`) and the **agent root** (the `agent-root:` line), both discovered dynamically from disk. These are

What's inside
Steps it walks through
  1. Pre-requisites
  2. Project Context
  3. Step 1: Detect mode and scope
  4. Step 2: Build the entity inventory
  5. When MODE = branch
  6. Plugin roots
  7. When MODE = sweep
  8. Out-of-scope files (both modes)
  9. Step 3: Per-entity audit
  10. Step 4: Cross-reference and bidirectional-link audit
  11. Step 5: Apply updates
  12. Step 6: Verify and report
Ships with 3 files
  • references/audit-checklist.md
  • references/scope-mapping.md
  • scripts/detect-doc-update-context.sh
More from han
All skills →
About this skill
What does the han-update-documentation skill do?

Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han re

How do I install it?

Run `npx skills add testdouble/han --skill han-update-documentation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From testdouble/han, a repository with 154 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going