AnaCataVC

ami-commit-planner

Analyzes the working tree for uncommitted work, proposes a structured set of commits, waits for user approval, and executes them.

ami-release-tagger

Must be triggered before any release or version bump. Analyzes git commits since the last tag and determines the next semantic version. Handles stable, QA, and RC tags.

ami-doc-manager

Comprehensive documentation manager. Automatically detects whether to architect new project documentation from scratch or synchronize existing documentation with code changes.

ami-context-researcher

Investigates external context, forces the AI to search for up-to-date documentation, and saves findings to external-references to prevent context loss.

Data & Documents Listed

ami-data-validator

Validates structural consistency between code changes and data definitions (DB connections, queries).

Analyzes the project's libraries and dependencies. It checks for unused dependencies, outdated versions, security vulnerabilities, and generates a structured report of the project's dependency health.

ami-doc-architect

Helps generate project documentation. Scans the repo to understand its structure, adapts to existing documentation styles, proposes a documentation strategy if starting from scratch, and interactively builds out the docs.

DevOps & Infrastructure Listed

ami-expert-council

Spawns a council of specialized subagents tailored to discuss, debate, and refine a user's idea or proposed change from multiple perspectives.

Data & Documents Listed

ami-learnings-extractor

Analyzes recent code changes to extract architectural decisions, lessons, patterns, and surprises, documenting them for future reference.

ami-methodical-debugger

Must be triggered whenever the user asks to solve a problem, fix a bug, or debug an issue. Performs an organized debugging process, systematically isolating the root cause without assumptions, and concludes by writing tests and documentation to prevent regressions.

ami-pr-comment-analyzer

Analyzes code review comments left by other developers on an active Pull Request, extracting pending tasks, suggestions, and offering to reply.

ami-pr-peer-reviewer

Assists in reviewing Pull Requests from other people. Understands the PR goal, reads available documentation, asks the user clarifying questions, focuses solely on modified code, and outputs quality observations with criticality levels.

ami-project-architect

Interactively sets up the initial architecture of a new project. It gathers requirements, researches technologies, proposes a stack and folder structure with constant user interaction, and finally scaffolds the initial files and a comprehensive README.md.

ami-release-drafter

Must be triggered before publishing any GitHub release. Analyzes git commits to automatically draft comprehensive bilingual release notes (English and Spanish) grouped by feature, bug fix, and maintenance.

ami-tech-debt-scanner

Analyzes the repository for technical debt, including outdated dependencies, dead code, duplication, and architectural inconsistencies. Provides a classified report based on criticality, effort, and risk.

ami-docs-updater

Must be triggered when code changes affect documented APIs, interfaces, or public behavior. Identifies if codebase documentation exists and updates it to reflect the changes.

ami-pr-conflict-detector

Must be triggered before creating or proposing any Pull Request. Identifies overlapping changes and merge conflicts with other open PRs.

ami-pr-self-reviewer

Acts as a critical self-reviewer for your own Pull Requests (draft or published). Instead of just leaving comments, it analyzes the diff and proactively suggests and applies concrete code fixes.