DmitriyYukhanov
UserPersonal collection of Claude Code plugins and skills: development workflows, cross-model review, issue-to-PR automation
Categories
Indexed Skills (26)
collaborative-loop
Sequential drive/validate/act collaboration between Claude and Codex. Claude analyzes, Codex validates each finding, both models must agree before action. Use when you want iterative improvement with bilateral consensus.
cross-review
Parallel dual review between Claude and Codex. Both models review independently. Findings confirmed by reviewer agreement, cross-validation, or evidence research are auto-applied each round; only genuinely inconclusive disagreements surface for user decision. Use for reviewing existing work with independent perspectives.
humanizer
Use when removing AI-generation patterns from text in English or Russian. Auto-detects language by Cyrillic ratio and applies the matching ruleset. Trigger phrases: "humanize this", "remove AI patterns", "make this sound human", "очеловечить текст", "убрать признаки нейросети", "сделай текст живым". Honors explicit overrides like "humanize as English" / "обработай как русский". For mixed-language text, asks which ruleset to apply.
issue-to-pr
Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card, then merges and cleans up once you approve the PR in-session. Triggers: "take task N", "work on issue #N", "do the next task", "build/fix X" when no issue exists yet, and — for the merge gate later — "merge it", "approve the PR", "ship it", "lgtm merge".
research
Internal forked research sub-skill for issue-to-pr. Runs raw codebase exploration in an isolated subagent and returns a short, cited summary, so the main pipeline's context is never flooded with file dumps. Not for direct use.
tune
Process the issue-to-pr friction log into concrete skill/script improvements. Reads .claude/issue-to-pr/friction.log, proposes batched edits with evidence, and applies them on your approval. Run it when the log has built up.
python-architect
Creates high-level Python architecture with protocols, test stubs, and module structure. Use when designing Python projects or features.
voice-to-text-config
Set up Telegram voice message transcription — checks faster-whisper installation, downloads the Whisper model, and verifies the hook works end-to-end. Use when the user asks to "set up voice transcription", "configure whisper", "fix voice messages", or when the transcription hook reports that whisper is missing or the model isn't downloaded.
typescript-architect
Creates high-level TypeScript architecture with interfaces, test stubs, and module structure. Use when designing TypeScript/JavaScript projects or features.
unity-architect
Use when designing Unity architecture, creating component hierarchies, defining interfaces, or generating test stubs and Mermaid diagrams for Unity projects
unity-dev
Start Unity C# development workflow with architecture, implementation, review, and testing phases
agent-teams
Set up and orchestrate Claude Code agent teams - multiple Claude Code instances working together with shared tasks, inter-agent messaging, and centralized management. Use when the user wants to (1) create or start an agent team for parallel work, (2) configure agent team settings like display mode or teammate mode or permissions, (3) coordinate teammates for code review or debugging or feature development or research, (4) understand when to use agent teams vs subagents, (5) troubleshoot agent team issues. Triggers include mentions of "agent team", "team of agents", "parallel agents", "teammates", "split pane", "tmux teammates", "delegate mode", "spawn teammates", or wanting multiple Claude instances collaborating.
implementation-prd
Create implementation-ready PRD/spec bundles for new apps, products, services, platforms, mobile or desktop software, SaaS systems, or complex features. Use when the user asks for a detailed PRD, build-ready spec, spec bundle, spec packet, PRD + contracts + schema + test plan, backend or API spec, frontend or mobile app spec, feature requirements, technical product brief, or documentation that Claude Code or Codex can implement with minimal follow-up or one-shot implementation. Produce a decisive bundle with PRD, contracts, storage or data-model artifact, test plan, acceptance criteria, default technical choices, and phased implementation order.
analyze
Reads input artifact(s) — codebase, planning session, refactor plan, or generic doc — and writes a tour-spec.json describing sections, embedded sources, cross-refs, quizzes, and external link maps. Use when the user wants a fresh learning guide built from source material; auto-hands-off to learning-guide:render. Trigger phrases — "create a learning guide for X", "make an interactive tour", "generate onboarding doc", "build a learning module".
render
Renders an existing tour-spec.json to a self-contained interactive HTML guide via the bundled Node renderer. Use when the user has hand-edited a tour-spec.json, when learning-guide:analyze hands off after drafting, or when the user explicitly asks to "render the tour", "regenerate the HTML", or "update the embedded sources". Idempotent for generated artifacts; preserves user-edited README and tour-spec.json.
lsp-setup
This skill should be used when the user asks to "set up LSP", "configure LSP", "install LSP", "enable LSP", "language server setup", "add LSP to project", "configure language server", "set up code intelligence", "validate LSP", "check LSP setup", "fix LSP", "LSP not working", or wants to enable or troubleshoot LSP-powered navigation (go-to-definition, find-references, hover, diagnostics) in Claude Code for a project.
python-coder
Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.
python-testing
Python testing patterns with pytest including unit tests, integration tests, fixtures, mocking, and coverage. Use when writing Python tests.
tg-alerts
Use when adding Telegram error notifications to any project. Guides through bot creation with @BotFather, chat/channel/forum-topic ID discovery, alert service implementation with deduplication and graceful failure, and framework-specific integration for Python (async/sync) and Node.js.
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.
unity-coder
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns
unity-run
Use when running Unity from CLI for any purpose — builds, tests, method execution, asset imports. Handles Unity installation detection, batchmode execution, and log monitoring. Other unity-dev skills depend on this for CLI execution.
unity-tests-write
Use when writing Unity tests, including EditMode tests, PlayMode tests, performance testing, and code coverage
unity-tests-run
Run Unity Test Framework tests via CLI batchmode with auto-detection of Unity installation
learning-guide
Use when the user asks to "create a learning guide", "make an interactive tour", "generate onboarding doc", "build a learning module", or any variant of turning an artifact (codebase, planning session, refactor plan, design doc) into an interactive HTML guide. Dispatches to learning-guide:analyze for new tours or learning-guide:render for re-renders after spec edits. Also use when the user is uncertain which step they need.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.