AnaCataVC
UserSkills and agents for Claude and Gemini
Categories
Indexed Skills (48)
ami-architect-project
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-plan-feature
Feature planning and orchestration workflow. Takes a raw idea, investigates external context and internal codebase, drafts a comprehensive implementation plan, and orchestrates execution.
ami-plan-commits
Analyzes the working tree for uncommitted work, proposes a structured set of commits, waits for user approval, and executes them.
ami-draft-release
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-research-context
Investigates external context, forces the AI to search for up-to-date documentation, and saves findings to external-references to prevent context loss.
ami-stress-test-idea
Conducts an adversarial stress-test and premortem analysis on technical proposals, architectures, or features before implementation. Exposes SPOFs, race conditions, cost explosions, and edge-case failure modes.
ami-manage-docs
Comprehensive documentation and knowledge manager. Architects new documentation, synchronizes wikis with code diffs, and audits knowledge bases to prune obsolete learnings and ephemeral files.
ami-extract-learnings
Analyzes recent code changes to extract architectural decisions, lessons, patterns, and surprises, documenting them for future reference.
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-data-validator
Validates structural consistency between code changes and data definitions (DB connections, queries).
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-quality-auditor
Performs a deep code quality, security, and structure audit on modified files.
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
Use ONLY when reviewing Pull Requests authored by OTHER PEOPLE (peer review). It focuses on generating code review observations with criticality levels and drafting review comments for teammates. If reviewing your OWN Pull Request or branch to apply local fixes before publishing, use ami-pr-self-reviewer instead.
ami-pr-self-reviewer
Use ONLY when reviewing YOUR OWN Pull Requests, local branches, or work-in-progress code before publishing. Instead of leaving comments, it acts as a stringent Senior Engineer to proactively find flaws and apply concrete code fixes locally. If reviewing a teammate's or another person's Pull Request to leave review comments, use ami-pr-peer-reviewer instead.
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.
ami-dependency-analyzer
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.
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.
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-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-pr-conflict-detector
Must be triggered before creating or proposing any Pull Request. Identifies overlapping changes and merge conflicts with other open PRs.
ami-dashboard-builder
Build high-impact interactive web dashboards and publication-quality Python data visualizations. Translates analytical datasets and KPIs into responsive visual narratives.
ami-data-profiler
Perform exploratory data analysis (EDA) and data quality auditing on datasets and DataFrames. Quantifies null distributions, identifies anomalies, and reviews methodologies for bias and statistical validity.
ami-sql-optimizer
Write, translate, and optimize high-performance SQL queries across major database engines. Diagnoses execution anti-patterns, recommends indexing strategies, and refactors complex joins into clean CTEs.
ami-test-strategist
Design comprehensive testing strategies and quality assurance architectures before tests are coded. Formulates test pyramid distributions, mocking boundaries, and CI quality gates.
ami-guide-next-step
Project guide workflow. Use this to scan the project's health across multiple dimensions, prioritize code quality, debt, tests, and documentation, and figure out what to do next.
ami-tag-release
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-analyze-dependencies
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-analyze-pr-comments
Analyzes code review comments left by other developers on an active Pull Request, extracting pending tasks, suggestions, and offering to reply.
ami-audit-quality
Performs a deep code quality, security, and structure audit on modified files.
ami-build-dashboard
Build high-impact interactive web dashboards and publication-quality Python data visualizations. Translates analytical datasets and KPIs into responsive visual narratives.
ami-debug-issue
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-design-test-strategy
Design comprehensive testing strategies and quality assurance architectures before tests are coded. Formulates test pyramid distributions, mocking boundaries, and CI quality gates.
ami-detect-pr-conflicts
Must be triggered before creating or proposing any Pull Request. Identifies overlapping changes and merge conflicts with other open PRs.
ami-optimize-sql
Write, translate, and optimize high-performance SQL queries across major database engines. Diagnoses execution anti-patterns, recommends indexing strategies, and refactors complex joins into clean CTEs.
ami-profile-data
Perform exploratory data analysis (EDA) and data quality auditing on datasets and DataFrames. Quantifies null distributions, identifies anomalies, and reviews methodologies for bias and statistical validity.
ami-review-peer-pr
Use ONLY when reviewing Pull Requests authored by OTHER PEOPLE (peer review). It focuses on generating code review observations with criticality levels and drafting review comments for teammates. If reviewing your OWN Pull Request or branch to apply local fixes before publishing, use ami-review-self-pr instead.
ami-review-self-pr
Use ONLY when reviewing YOUR OWN Pull Requests, local branches, or work-in-progress code before publishing. Instead of leaving comments, it acts as a stringent Senior Engineer to proactively find flaws and apply concrete code fixes locally. If reviewing a teammate's or another person's Pull Request to leave review comments, use ami-review-peer-pr instead.
ami-scan-tech-debt
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-validate-data
Validates structural consistency between code changes and data definitions (DB connections, queries).
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-test-creator
Must be triggered when new functionality is added and no existing tests cover the changes. Automatically generates tests for modified code.
ami-create-tests
Must be triggered when new functionality is added and no existing tests cover the changes. Automatically generates tests for modified code.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.