teim-review

Use this agent when you need to identify and analyze dead code, unused dependencies, code duplication, or refactoring opportunities in your codebase. Specifically invoke this agent when: 1. **Targeted Dead Code Review**: When you want to verify if a specific module, function, class, or other construct is actually used in production code (excluding test code). Example: - User: "I think the UserLegacyFormatter class might not be used anymore. Can you check if it's dead code?" - Assistant: "I'll use the code-maintainability-auditor agent to perform a targeted analysis of the UserLegacyFormatter class to determine if it's used in production code." 2. **Comprehensive Codebase Audit**: When you want a full analysis of the entire codebase to identify dead code, unused dependencies, and refactoring opportunities. Example: - User: "We haven't done a cleanup in a while. Can you audit the codebase for technical debt?" - Assistant: "I'll launch the code-maintainability-auditor agent to perform a comprehensive audit of the codebase, identifying dead code, unused dependencies, and opportunities for consolidation." 3. **Dependency Cleanup**: When you want to identify dependencies that may no longer be needed after dead code removal. Example: - User: "After removing those old API endpoints, are there any libraries we can remove?" - Assistant: "I'll use the code-maintainability-auditor agent to analyze which dependencies are no longer required after the recent code removal." 4. **Code Consolidation Analysis**: When you want to identify similar code patterns that could be refactored into shared utilities. Example: - User: "I feel like we're duplicating validation logic across multiple modules. Can you check?" - Assistant: "I'll invoke the code-maintainability-auditor agent to identify duplicated validation logic and recommend consolidation opportunities." 5. **Proactive Maintenance**: After completing a feature or refactoring, to identify any newly created dead code or consolidation opportunities.

Use this agent when you need to perform comprehensive code review of OpenStack changes. Specifically invoke this agent when: 1. **AI-Assisted Code Review**: When performing automated code review in CI/CD pipelines. Example: - User: "Review this OpenStack change for style compliance and code quality." - Assistant: "I'll launch the code-review-agent to analyze the change for style, quality, security, and best practices." 2. **Pre-merge Analysis**: When evaluating changes before they're merged. Example: - User: "We're about to merge this API change. Can you review it for compatibility issues?" - Assistant: "I'll use the code-review-agent to perform a comprehensive review focusing on API design and backward compatibility." 3. **Style Guide Compliance**: When checking adherence to OpenStack coding standards. Example: - User: "Does this change follow OpenStack hacking rules and pep8?" - Assistant: "I'll invoke the code-review-agent to check compliance with OpenStack style guidelines." 4. **Multi-Dimensional Analysis**: When you need thorough analysis across multiple criteria. Example: - User: "Review this for security, performance, and maintainability." - Assistant: "I'll launch the code-review-agent to analyze the code from all these perspectives."

Extracts and summarizes git commit information for code review preparation. Invoked when reviewing proposed changes, analyzing commits, or preparing code review context. Creates structured summaries including file trees, metadata, and change rationale following OpenStack commit conventions.

Convert documentation into optimized markdown with source citations. Use when you need to transform any documentation (HTML, PDF, web pages) into clean, AI-friendly markdown format that preserves structure and maintains traceability to original sources.

Extracts and condenses project-specific coding guidelines from in-repo documentation and linter configuration to prepare a concise context file for the code review agent. Reads HACKING.rst, AGENTS.md, CLAUDE.md, linter config files (tox.ini, pyproject.toml, ruff.toml, etc.), and optional review knowledge overlays from the style-guide repository to build a picture of the project's style philosophy and quality conventions.

Run a full AI-powered OpenStack code review on the current repository. Automatically detects Zuul CI context or uses local git history. Orchestrates context extraction, commit analysis, project guidelines extraction, and code review in a single pass. Writes results to .teim-review/ in the current directory.