WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.
Agent for validating Aspire documentation against actual behavior. Use when auditing documentation accuracy, testing examples, or identifying discrepancies between documentation and implementation.
Discover and link related issues as dependencies. Searches for issues that should be connected and recommends dependency relationships to establish proper work order.
python's package managing
Generate high-quality conventional git commit messages and, with user approval, run the commit. Use when drafting or refining commit messages, validating commit quality, or committing staged work while avoiding noisy histories.
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
Run the project's formatter, linters, and mypy checks in the required order, fixing issues and managing any needed stub dependencies via uv.
Add purposeful debug logging to improve observability without changing behavior.
Perform structured, actionable code reviews for Python code with clear findings and suggestions.
Inspect a repository and draft an AGENTS.md file using the standard template, capturing commands, structure, and workflow rules.
How to use Colin to compile agent skills from live sources. Use when working with Colin projects, templates, compilation, or skill management.
{% set server = colin.mcp.source.server_info() %}
Agent skill compiled from company onboarding docs in Notion
Make HTTP requests with automatic x402 payment support using the purl command line interface.
Run smoke tests to verify extension functionality in a real VS Code environment. Use this when checking if basic features work after changes.
VS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling.
Critical patterns for cross-platform path handling in this VS Code extension. Windows vs POSIX path bugs are the #1 source of issues. Use this skill when reviewing or writing path-related code.
Run integration tests to verify that extension components work together correctly. Use this after modifying component interactions or event handling.
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major changes.