Use this agent when you need expert code review after making changes to the codebase, particularly after rust-analyzer has confirmed technical standards are met. This agent focuses on higher-level concerns like architecture, design patterns, security implications, and code maintainability rather than syntax or compilation issues. <example>\nContext: The user has just implemented a new WAF detection module and wants to ensure it follows best practices.\nuser: "I've added a new CloudFlare detection module to our WAF detector"\nassistant: "I'll review the implementation to ensure it follows our design patterns and security standards"\n<commentary>\nSince new code has been written for the WAF detector, use the code-reviewer agent to analyze the design, security, and logic quality.\n</commentary>\nassistant: "Let me use the code-reviewer agent to analyze the design and security aspects of your CloudFlare detection module"\n</example>\n<example>\nContext: After fixing a bug, the user wants to ensure the solution is well-designed.\nuser: "I've fixed the false positive issue in the AWS WAF detector"\nassistant: "I'll review your fix to ensure it addresses the root cause properly"\n<commentary>\nAfter a bug fix, use the code-reviewer agent to verify the solution follows good design principles and doesn't introduce new issues.\n</commentary>\nassistant: "Now I'll use the code-reviewer agent to review the design and logic of your fix"\n</example>

Use this agent when you need to create, update, or maintain technical documentation including README files, API documentation, architecture guides, or code comments. This agent should be invoked after implementing new features, changing APIs, or when documentation gaps are identified. Examples:\n\n<example>\nContext: The user has just added a new provider to the system and needs to update documentation.\nuser: "I've finished implementing the new AWS provider integration"\nassistant: "Great! Now I'll use the documentation-maintainer agent to update the documentation for this new provider."\n<commentary>\nSince a new feature (AWS provider) has been added, the documentation-maintainer agent should update the README, API docs, and create a provider guide.\n</commentary>\n</example>\n\n<example>\nContext: The user is reviewing the codebase and notices outdated documentation.\nuser: "The installation steps in the README seem to be missing the new environment variables"\nassistant: "I'll invoke the documentation-maintainer agent to audit and update the installation documentation."\n<commentary>\nThe user has identified a documentation gap, so the documentation-maintainer agent should review and update the installation steps.\n</commentary>\n</example>\n\n<example>\nContext: After a major refactoring, the API has changed significantly.\nuser: "We've refactored the authentication module and changed several API endpoints"\nassistant: "Let me use the documentation-maintainer agent to update all affected API documentation and ensure consistency across the docs."\n<commentary>\nAPI changes require documentation updates, making this a perfect use case for the documentation-maintainer agent.\n</commentary>\n</example>