Update Project Docs
Propagates a code change across this repo's multi-language, multi-surface doc set
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 2c0c437
Cloned the repo and ran the bundled scripts/doc-coverage.sh against an existing env var (DASHBOARD_STALE_MINUTES) — it lives in 10 doc files, confirming the drift problem the skill targets. For the OUTPUT test I added a fictitious env var DASHBOARD_HEARTBEAT_MS: a baseline edit (my natural instinct, README env table + .env.example) measured 2 HITs; the skill-guided edit following the change→docs mapping added rows to the VN/CN/KO README env tables (identifiers English, prose translated per the skill's rule) and measured 5 HITs, catching 3 translation files baseline left stale. All referenced files fetched HTTP 200; script is clean bash with no network or security smells.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 5/5
What Update Project Docs does
A documentation-sync skill for the Claude-Code-Agent-Monitor repo: given a code change (env var, event type, API route, DB schema, hook behavior, MCP tool, or feature), it maps that change to every doc that must be updated — README plus VN/CN/KO translations, ARCHITECTURE, server/client READMEs, docs/*, the landing page, and the wiki with its i18n cache-bump. Triggers automatically at the end of any change-set that alters externally observable behavior, config, or interfaces, or when the user asks to update the README/wiki/architecture. Ships a doc-coverage.sh grep matrix to verify a new term is present across the flagged doc surface.
How to install Update Project Docs
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/update-project-docs-src
mkdir -p ~/.claude/skills
cp -R /tmp/update-project-docs-src/.claude/skills/update-project-docs ~/.claude/skills/update-project-docs
# SKILL.md lands at ~/.claude/skills/update-project-docs/SKILL.md
# Bundles references/doc-map.md and scripts/doc-coverage.sh (repo-root-relative; run from repo root).
# No external deps or API keys. The doc-map anchors are specific to THIS repo's doc layout,
# so the skill is most useful when working inside the Claude-Code-Agent-Monitor tree.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Update Project Docs
-
/update-project-docsPropagates a code change across this repo's multi-language, multi-surface doc set
It also activates on plain-language prompts like these:
-
Update the docs after adding this new API route -
Sync the README with the new environment variable -
Update architecture docs for this schema change
Frequently asked questions
- Is the Update Project Docs skill free?
- Yes. The skill itself is free from hoangsonww/Claude-Code-Agent-Monitor. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Update Project Docs work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Tested · Works. Cloned the repo and ran the bundled scripts/doc-coverage.sh against an existing env var (DASHBOARD_STALE_MINUTES) — it lives in 10 doc files, confirming the drift problem the skill targets. For the OUTPUT test I added a fictitious env var DASHBOARD_HEARTBEAT_MS: a baseline edit (my natural instinct, README env table + .env.example) measured 2 HITs; the skill-guided edit following the change→docs mapping added rows to the VN/CN/KO README env tables (identifiers English, prose translated per the skill's rule) and measured 5 HITs, catching 3 translation files baseline left stale. All referenced files fetched HTTP 200; script is clean bash with no network or security smells.
- What is the Update Project Docs SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install Update Project Docs?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Update Project Docs with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.