스킬 찾기

Summarizes the current Claude Code conversation into an evidence-backed map of goals, changes in direction, completed outcomes, current work, and open decisions. Use it to regain context after interruptions, session switching, or conversation compaction.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Regaining context after switching sessions
• Reviewing progress after conversation compaction
• Identifying decisions that still need user input

Investigate why a bug, performance change, or experimental result occurred. Compare competing explanations using supporting and contradicting evidence, rank likely causes, and identify the next check that would best resolve uncertainty.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating bugs and regressions
• Explaining latency and resource usage
• Tracing unexpected experimental results

Make agent replies and progress reports concise while preserving exact code, commands, numbers, and meaning. The guidance puts conclusions first, removes filler, and uses complete wording whenever brevity would make warnings or instructions unclear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Shortening agent replies
• Making progress reports easier to scan
• Reporting errors with a clear next step

Set up, refresh, or repair oh-my-claudecode after a plugin, npm, or local development installation. Configure project or global instructions, status display, and team defaults, with quick updates for existing setups and support for resuming interrupted configuration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Configuring OMC after installation
• Updating project instructions after an OMC upgrade
• Choosing global configuration and preservation options

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying the destination of an early idea
• Mapping decisions and their dependencies
• Resuming unresolved decisions across sessions

Compare a UI screenshot with reference images and receive a structured JSON assessment. Get a score, pass or revision status, concrete visual differences, and suggested edits for layout, spacing, typography, colors, and visual hierarchy.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether an implemented screen matches its reference
• Finding differences in spacing, typography, and colors
• Prioritizing edits from structured visual feedback

Turns vague development requests into reviewed plans through planning, architecture, and quality-review agents. It compares alternatives, defines testable acceptance criteria, and records decisions, stopping before implementation unless execution has been explicitly approved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining the scope of a vague development request
• Comparing implementation approaches before coding
• Planning migrations or security-sensitive changes

Build a lasting Markdown knowledge base for project decisions, architecture, and session discoveries. Search pages by keywords and tags, use results to answer with citations, and check for outdated content, broken links, and structural problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preserving project decisions across sessions
• Finding past debugging discoveries
• Checking knowledge pages for broken links and stale content

Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing architecture after a batch of changes
• Investigating changes that touch too many files
• Prioritizing structural improvements

Turn support feedback or chat logs into a structured requirements document. Use numbered questions to clarify problems, goals, users, constraints, and open questions, then guide human review before handing approved requirements to development.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning support feedback into requirements
• Clarifying missing details in chat logs
• Recording requirements review and resubmission

Check whether a feature, fix, or refactor actually works using existing tests, build checks, direct commands, or manual validation. Get a concise account of the evidence, including what passed, what failed, and what remains unverified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking that a bug fix works
• Verifying a newly added feature
• Checking behavior after a refactor

Turn a successful workflow from the current session into a reusable OMC skill draft. Capture inputs, ordered steps, decision rules, pitfalls, and verification evidence, then choose an appropriate storage location.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preserving a hard-won debugging workflow
• Turning project-specific procedures into skill drafts
• Deciding whether a workflow belongs in a skill or documentation

Research a question by splitting it into two to five topics and assigning parallel documentation agents. Get a combined summary, detailed findings for each topic, and source URLs from web searches and documentation lookups.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Researching implementation best practices
• Comparing libraries for a project
• Looking up current framework conventions

Coordinate multiple agents on a shared task list to complete development work. Break tasks into clear responsibilities, manage dependencies, and move through planning, implementation, verification, and bounded repair cycles with recorded handoffs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fixing TypeScript errors across several modules
• Sharing build-error investigation among agents
• Implementing responsive layouts across pages

Break a development task into small requirements with explicit acceptance criteria, then repeat implementation and verification while saving progress. Completion depends on evidence for each requirement and reviewer approval, with configurable reviewers and a final cleanup check.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Carrying a multi-step implementation through verification
• Resuming work with recorded progress
• Tracking evidence for each requirement

Manage local oh-my-claudecode skills through commands and guided prompts. List and search available skills, create or edit custom ones, and compare or copy skills between personal and project folders to organize reusable instructions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Listing and searching local skills
• Creating a skill through guided prompts
• Editing skill instructions and trigger keywords

Stop active OMC workflows and clean up their runtime state while preserving progress where the mode supports resuming. It distinguishes the current session from all sessions and offers graceful shutdown or forced cancellation without bypassing ownership checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Stopping the current session's automated workflow
• Pausing Autopilot while keeping progress for resuming
• Shutting down a running agent team

Investigate questions that need answers before work can proceed. Search repository code and documents, consult official technical documentation, and return sourced findings that separate verified facts, inferences, conflicting evidence, and remaining unknowns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking code behavior before choosing a change
• Investigating SDK or API details in official documentation
• Tracing behavior through files, callers, and history

Review records across OMC sessions to find recurring obstacles in the agent's working environment. It turns evidence from timelines, logs, and notes into ranked proposals for checks, guidance, tools, or information access, with changes requiring user approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating errors repeated across sessions
• Reviewing missing or disconnected automated checks
• Improving access to logs and service state

Turn a short product idea into working code through requirements analysis, technical planning, implementation, testing, and review. It coordinates agents across these stages, fixes detected problems, and reports assumptions that still need a human decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a product from a short idea
• Creating a bookstore inventory API
• Developing a habit-tracking command-line tool

Draft a pull request description from existing project records and verification results. Present the change with a compact visual, before-and-after evidence, rollback details, and its wider impact so reviewers can assess the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a pull request description
• Explaining a refactor with a compact diagram
• Presenting existing before-and-after check results

Create separate Git working directories for issue fixes, pull request reviews, and feature development. Optional tmux terminal sessions help manage parallel tasks, return to ongoing work, and clean up completed sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Working on several issue fixes in parallel
• Preparing a separate workspace for a pull request review
• Returning to an ongoing development session

Organize useful findings from a session and save them in the right place: project memory, temporary notes, or lasting documentation. The skill separates reusable facts from working context and flags duplicate, outdated, or conflicting information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving reusable project findings from a session
• Separating temporary notes from lasting knowledge
• Keeping conventions in the appropriate documentation

Find the appropriate skill for the work you need to do, from clarifying requirements to implementation, review, and verification. This routing guide selects the next skill or shows a manual command without performing the work itself.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a skill for unclear requirements
• Finding the next step after plan approval
• Locating debugging or verification skills