코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Unified entry point for creating or updating OpenCode tools (skills, agents, commands) with dependency awareness. Orchestrates the creation of multiple related artifacts in a single session. Use when user says "create opencode tool", "new opencode tool", "oc-tool-dev", or wants to create/update an OpenCode artifact and may need supporting artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates an existing OpenCode command to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode command", "fix opencode command", "migrate command to opencode", or wants to modernize an existing OpenCode command file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert Claude Code plugins into generic, platform-agnostic format. Supports full conversion (skills, agents, hooks), flatten mode (skills only — agents converted to skills, hooks absorbed), or nested mode (agents nested as pure markdown within parent skills, hooks absorbed). Full mode supports per-group or unified output layouts — unified merges all groups into a single directory organized by component type. Strips Claude Code-specific implementation details to produce clean markdown files preserving only the intent and instructions. Use when asked to "make this portable", "convert to generic format", "export plugin", "create universal skills", "strip platform dependencies", "make harness-agnostic", "decouple from Claude Code", "flatten to skills only", "nest agents in skills", or when the user wants their plugin content usable outside Claude Code. Also use when the user wants to share skills with teams using different agent frameworks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides through creating a new OpenCode command with interactive interview, $VARIABLE configuration, and validation. Use when user says "create opencode command", "new opencode command", "build command for opencode", or wants to create an OpenCode command markdown file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates an existing OpenCode agent to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode agent", "fix opencode agent", "migrate agent to opencode", or wants to modernize an existing OpenCode agent file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates an existing OpenCode skill to match current platform best practices, fixes deprecated patterns, and validates the result. Use when user says "update opencode skill", "fix opencode skill", "migrate skill to opencode", or wants to modernize an existing OpenCode SKILL.md file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Converts Agent Alchemy plugins into formats compatible with other AI coding platforms
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear, conventional git commit messages from staged changes. Use when the user asks to commit work, write a commit message, or clean up a commit history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug failing webhooks. Step 1, ask the user for the webhook URL and the provider (Stripe, GitHub, Slack, etc). Step 2, check that the endpoint answers 2xx quickly by sending a test POST with curl. Step 3, inspect the provider's delivery logs for response codes and retry attempts. Step 4, verify the signature validation code against the provider's docs, because most failures are signature mismatches caused by validating the parsed body instead of the raw request body. Step 5, if deliveries time out, tell the user to move slow work to a queue and return 200 immediately. Step 6, replay a failed delivery and confirm it is processed end to end. Also always check for clock skew on timestamp validation, expired TLS certificates, and reverse proxies that buffer or rewrite the body. Always tell the user which step found the problem. Use this skill whenever webhooks are mentioned in any way.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for large-scale refactorings with Mikado and Strangler Fig. Use for architecture migration, library replacement, module splitting, or pattern changes. Maintains a Mikado graph to track dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Advanced code review with multiple sequential agents. Customize for your project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Follow-up review that never trusts a commit message — always re-reads the actual diff before resolving a thread. Cites a real source for new issues, matching review-advanced.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code review avancée avec plusieurs agents séquentiels. À personnaliser pour votre projet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git worktree management for working on multiple branches in parallel. Create, list, remove, and synchronize worktrees. Protects against direct pushes to master.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous refactoring via spec-driven development. Orchestrates contract tests, batch planning, and incremental implementation with regression checks. Reuses feature-planner and feature-implementer agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean Code (Robert C. Martin) guide to produce and challenge code that is readable, durable, simple, and consistent. Covers naming, functions, comments, smells, and refactor heuristics. Complements `/solid` (SOLID principles) and `/anti-overengineering` (YAGNI/KISS). Activate during the REFACTOR phase of the TDD cycle and during implementation self-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Anti-overengineering guide based on YAGNI. Use before adding an architectural pattern, during code review, or to challenge an overly complex implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Basic code review skill template. Customize for your project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Event Storming Big Picture on a bounded context or the whole project. Explores code to discover domain events, commands, entities, context boundaries, and produces structured markdown following Vaughn Vernon's strategic patterns. Usage: /event-storming <bc-name> or /event-storming global
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Template de code review basique. À personnaliser pour votre projet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.