agent-doc-writer

You can automate documentation updates by analyzing git diffs to categorize code changes into types like New Feature or Bug Fix, which then determines the necessary documentation scope and generates structured content recommendations.

Determining documentation scope involves categorizing the code change to assess its impact, ranging from a simple commit message to updating a README or creating a dedicated documentation file with suggested content.

Yes, after a code review you can receive structured recommendations with specific action items and suggested content for maintaining technical documentation based on the analyzed code modifications.

Code change analysis categorizes modifications into types like Refactor or Breaking Change to evaluate their impact, subsequently recommending the appropriate documentation level from inline comments to dedicated files.

You need to provide a standard git diff output so the analysis can evaluate the nature and impact of your code modifications to recommend appropriate documentation updates.

Automating recommendations for breaking changes ensures your technical documentation stays current with development by identifying the required documentation scope and providing structured content suggestions.