Agent for validating Aspire documentation against actual behavior. Use when auditing documentation accuracy, testing examples, or identifying discrepancies between documentation and implementation.
CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.
Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Discover and link related issues as dependencies. Searches for issues that should be connected and recommends dependency relationships to establish proper work order.
Add purposeful debug logging to improve observability without changing behavior.
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.
Perform structured, actionable code reviews for Python code with clear findings and suggestions.
Run the project's formatter, linters, and mypy checks in the required order, fixing issues and managing any needed stub dependencies via uv.
Inspect a repository and draft an AGENTS.md file using the standard template, capturing commands, structure, and workflow rules.
python's package managing
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
Generate a codebase health snapshot for technical debt tracking and planning. Analyzes git history, code complexity, debt markers, and dependencies to identify hotspots and refactoring priorities.
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major 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.
Debug a failing test using an iterative logging approach, then clean up and document the learning.