Update Docs
Update project documentation after implementing a feature. Use when: updating docs, documentation, update docs after implementation. Do not use: for doc-first design, specification writing.
Install
$ agentstack add skill-woliveiras-geremmyas-update-docs ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Update Docs
Update documentation in docs/ after a feature is implemented.
When to Use
- After finishing a feature implementation
- When specs, code, or architecture changed and docs are stale
- When onboarding docs need to reflect new patterns
Procedure
- Read the spec for the implemented feature (from
specs/or the conversation) - Read the implemented code to understand what actually shipped
- Search
docs/for existing documentation that may need updates - For each affected doc:
- If it exists: update the relevant sections, preserving the existing format
- If it doesn't exist: create it following the format of neighboring docs
- Check for broken references (links to moved/renamed files)
What to Document
- API changes: new endpoints, changed parameters, updated responses
- Architecture changes: new modules, changed boundaries, new patterns
- Setup changes: new dependencies, changed build steps, new env vars
- Configuration changes: new settings, changed defaults
Rules
- Match the existing documentation style and format
- Do NOT rewrite docs that don't need changes
- Keep docs concise — one paragraph per concept, not walls of text
- Update the table of contents if the doc has one
- If no
docs/directory exists, create it with a README
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: woliveiras
- Source: woliveiras/geremmyas
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.