update-project-docs

This skill appears to do what it claims, but review these precautions before use: - Be aware the first-run full audit reads the entire repository and may run project build/lint/docs commands which execute code from the repo. Run it in a safe environment (local dev machine you control, a disposable container, or CI sandbox) rather than an environment with sensitive credentials. - Require explicit confirmation before the skill stages or commits changes. Prefer that the skill prepares a diff or branch and asks you to inspect/approve before committing. - Back up important or sensitive files and ensure no secrets are stored in docs that could be accidentally committed. Inspect the `.docs-sync` location and contents after the run. - If you want to be conservative, run a dry-run/read-only audit first (no commits, no script execution) to get a list of proposed changes, then run an update pass in a branch you control. - If you are using autonomous agents, restrict this skill's ability to run without user approval — automated commits or builds increase blast radius. If you want me to check the SKILL.md for specific commands the agent would run in your environment (or to produce a safe dry-run plan), I can do that.