Bellman

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

Documents a codebase with linked AGENTS.md files that explain each directory, important files, dependencies, and working rules. It can also update existing documentation while preserving human-written notes and checking that the document hierarchy remains consistent.

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

• Documenting an unfamiliar codebase for AI agents
• Recording directory-specific rules and dependencies
• Updating documentation after structural changes

Define repeatable workflows and their dependencies in JSON, then execute them through a CLI. Combine commands, read-only agent tasks, parallel branches, and human approval steps, with journal records that support recovery after interruption.

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

• Running repeatable build and test workflows
• Resuming a workflow after a crash
• Adding human approval before deployment

Resolve a design question by building a temporary, runnable prototype. Explore logic through clickable scenarios or compare three structurally different interface variants, then record the user's decision while keeping the prototype separate from production code.

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

• Comparing three different interface structures
• Exploring state transitions through clickable scenarios
• Resolving design discussions that need a visible example

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

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

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

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

Carry an agreed development task through implementation and verification. Make small changes that follow existing patterns, divide independent work when useful, and report changed files, evidence that the code works, and any remaining issues.

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

• Implementing an agreed feature
• Making a small code fix and verifying it
• Splitting independent development tasks

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

Prepare and guide software releases using rules discovered in the project and its automated build workflows. It tracks version files, helps draft release notes, runs release steps with confirmation, and checks the published result.

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

• Preparing a software version release
• Updating version numbers across multiple files
• Drafting release notes from commit history

Turn a vague idea into a written specification through focused questions. The skill scores clarity across goals, constraints, and success criteria, explores hidden assumptions, and requires explicit approval before moving from planning to execution.

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

• Clarifying a vague idea before implementation
• Defining goals, constraints, and acceptance criteria
• Checking requirements across multiple project components

Turn a development idea into an actionable plan with implementation steps, testable acceptance criteria, and risk mitigations. Gather requirements through focused questions, generate plans directly from detailed requests, or review proposals from multiple perspectives.

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

• Clarifying requirements for a vague development idea
• Planning implementation from detailed requirements
• Comparing design options from multiple perspectives

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

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

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

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

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

• Clarifying instructions in CLAUDE.md
• Making specifications and tickets actionable
• Adding completion criteria to skill procedures

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

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

Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.

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

• Requesting a security review of a patch
• Seeking UX suggestions for a user flow
• Drafting an implementation plan for an issue

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

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

Keep code changes small by checking whether they are needed, reusing existing helpers, and choosing standard or available tools first. It guides planning and implementation while preserving validation, security, accessibility, and the functionality the user requested.

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

• Implementing a feature with a small code diff
• Bringing an expanding implementation back within scope
• Checking for reusable code before adding helpers

Explain code structure, execution flow, and proposed changes with a focused visual, such as pseudocode, a tree, a Mermaid diagram, or a diff. Use a single HTML artifact when a richer layout is needed.

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

• Explaining branches and function call order
• Showing UI, module, or file responsibilities
• Comparing structure before and after a change