Doc Updater

Analyze Context: Determine what kind of update is needed based on recent changes or user request.

• Feature/Fix: Update CHANGELOG.md and potentially feature-specific docs in docs/.
• New Command/API: Update API documentation (create if missing).
• Setup/Config: Update README.md (Installation/Usage sections).

CHANGELOG Update: If updating CHANGELOG.md:

• Read E:\Tepora_Project\CHANGELOG.md.
• Identify the current "Unreleased" section or create a new entry for today's date.
• Categorize the change (Added, Changed, Deprecated, Removed, Fixed, Security).
• Format: - [Category] Description of the change.

README Update: If updating README.md:

• Read the file first.
• Locate the relevant section (e.g., "Getting Started", "Features").
• Appending or modifying text to reflect the current state of the project.
• Critical: Ensure installation commands and requirement versions are accurate.

Architecture/API Docs: If deeper documentation is needed:

• Check docs/ directory.
• If a relevant file exists, update it.
• If not, ask the user if a new documentation file should be created (e.g., docs/api-reference.md).

Review & Write:

• Present the planned changes to the user (diff format is helpful).
• Upon confirmation, write the changes to the files.