Update Docs on Code Change
v1.0.0Automatically update README.md and documentation files when application code changes require documentation updates. Use when adding new features, changing AP...
⭐ 0· 40·0 current·0 all-time
byJohn Haugabook@jhauga
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (update docs on code change) match the content of SKILL.md. The skill does not request unrelated binaries, credentials, or config paths — everything requested (none) is proportional to the stated purpose.
Instruction Scope
SKILL.md contains broad, high-level procedures for when/how to update README, API docs, changelogs, and migration guides. It does not include explicit commands, external endpoints, or requests for secrets, but it is intentionally open-ended (e.g., 'verify examples still compile/run', 'access to code changes') which grants implementation discretion to the agent. That vagueness could lead an agent to run build/test commands or modify repository files if given repository access — expected for the purpose but worth reviewing in deployment.
Install Mechanism
No install spec and no code files. This is the lowest-risk pattern: the skill only provides prose instructions and nothing is written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. SKILL.md references repository files (README.md, docs/) which is appropriate. There are no unexpected requests for secrets or unrelated service tokens.
Persistence & Privilege
always is false and the skill does not request persistent system-wide modifications. It does not claim to modify other skills or agent-wide settings. Autonomous invocation is allowed (platform default) but is not combined with elevated privileges.
Assessment
This skill is instruction-only and internally consistent with its purpose, but it is intentionally high-level and will rely on whatever repository and tooling access the agent already has. Before enabling it: (1) review and limit the agent's repository and CI permissions to least privilege (read vs write, ability to push/commit), (2) confirm whether the agent is allowed to execute build/tests in your environment (these steps can run arbitrary code), (3) require human review or PR workflow for doc commits if you don't want automated pushes, and (4) monitor for unexpected network or credential access because the skill's prose could lead an agent to call external services depending on implementation. If you want stricter behavior, require the skill to only produce suggested edits as PR comments rather than making commits automatically.Like a lobster shell, security has layers — review code before you run it.
latestvk971djw19k17r9ekr25cskn81h83zwxh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.