altinity-mcp

Register a temporary MCP connector in claude.ai and/or chatgpt.com, verify it works, then offer cleanup. Trigger when the user wants to test an MCP server URL through a real AI frontend — phrases like "test mcp", "add test connector", "smoke-test mcp server", "register connector for testing", "check mcp in claude", "check mcp in chatgpt".

Use when asked to review a PR, commit, commit range, branch, patch, or pasted diff for duplicated functionality, reinvented wheels, not-invented-here patterns, parallel abstractions, inconsistent naming, inconsistent settings/APIs/schemas/metrics/errors/logs, redundant config keys, non-standard implementations, or places where new code should reuse, generalize, extend, or align with existing codebase patterns and user-facing conventions. Language-agnostic — works on Go, C++, Python, TypeScript, etc. Triggers on phrases like "review for duplication", "consistency review", "is this already implemented", "does this match our conventions", "reinventing the wheel", "is there a helper for this".

Use when the user asks for a multi-perspective review of a Go diff, PR, branch, commit range, or commit hash. Triggers on requests like "review this PR", "umbrella review", "do a full review", "deep review of branch X", or any Go-codebase code review where multiple independent angles (security, perf, concurrency, lifetime, compat, tests, etc.) should be considered before producing a consolidated report. Adapted for altinity-mcp from the upstream ClickHouse `umbrella-clickhose-review` skill — same workflow, Go-flavored subagents (drops C++ headers + lifetime; reframes security around OAuth/secret-handling, perf around GC/goroutines/channels, compat around helm-chart/image-rolling/OAuth-config rename).