Agent skill
udoc
Update documentation and generate changelog from task implementation
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/udoc
SKILL.md
Update Documentation (UDOC)
PRIMARY OBJECTIVE
Generate documentation updates and changelog entries from a completed task implementation.
CONTEXT
Use when:
- Task implementation is complete (before or after PR/merge)
- Documentation needs updating to reflect code changes
- Changelog entry needed for the task
WORKFLOW
STEP 1: Resolve Task Path
- Parse
$ARGUMENTSfor a task directory path - If not provided — Ask: "Which task to update docs for? Provide task directory path (e.g.,
tasks/task-2026-02-09-feature-name/)." - Validate: find
tech-decomposition-*.mdinside the task directory - If not found — error with available task directories
STEP 2: Update Documentation (docs-updater agent)
Call docs-updater agent:
Task: "Update documentation based on task implementation"
Prompt: "Review the task document at [TASK_DOCUMENT_PATH] and update all relevant documentation files based on the implemented changes. Return a summary of what documentation was updated."
Capture the summary of documentation changes.
STEP 3: Generate Changelog (changelog-generator agent)
Call changelog-generator agent:
Task: "Generate changelog entry for completed task"
Prompt: "Generate a changelog entry based on the task document at [TASK_DOCUMENT_PATH] and documentation updates: [DOCS_UPDATES_SUMMARY]. Include the main feature implementation and any documentation changes."
Capture the changelog entry.
STEP 4: Commit (Optional)
- Show user what changed:
git diff --statfor modified files- Brief summary from both agents
- Ask: "Commit these documentation and changelog updates?"
- If approved:
bash
git add docs/ git commit -m "docs: update documentation and changelog - Documentation updates: [DOCS_SUMMARY] - Changelog entry: [CHANGELOG_SUMMARY] Generated by docs-updater and changelog-generator agents." - If on a feature branch, ask whether to push
STEP 5: Summary
Report to user:
Documentation updated!
**Docs**: [list of updated files]
**Changelog**: docs/changelogs/YYYY-MM-DD/changelog.md
**Committed**: Yes/No
ERROR HANDLING
- Task not found: List available task directories under
tasks/ - No changes detected: Inform user, suggest checking if docs are already up to date
- Agent fails: Report which agent failed, suggest running manually
SUCCESS CRITERIA
- Task document found and analyzed
- Documentation updated for affected files
- Changelog entry created in correct date directory
- User informed of all changes
- Changes committed only with user approval
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?