개발 스킬

Design commands and processing loops that reach the same final state after retries or crashes. Use the current state to apply only necessary changes, and make leftover locks, files, or records recognizable during the next run.

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

• Design commands that can be safely rerun
• Review recovery after a crash
• Handle leftover locks and temporary files

Guides additions, refactors, and rewrites by removing unnecessary complexity first. It prioritizes deleting dead code, redundant checks, empty references, and repetitive prompt instructions, then building around observed usage and explicit requirements.

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

• Cleaning up code before adding a feature
• Planning removal steps before a refactor or rewrite
• Reviewing checks added for speculative edge cases

Reviews the current conversation from three perspectives to find reusable lessons and propose concrete skill improvements. It separates findings into accepted, rejected, and backlog items, with user approval required before applying accepted edits.

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

• Reviewing lessons from a completed agent session
• Turning repeated mistakes into skill improvements
• Separating skill edits from structural fixes

Review code comments in selected files or changes with a dedicated agent, remove accepted findings, and fix underlying problems. It also proposes ways to enforce documented constraints through types, runtime checks, tests, or automated checks.

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

• Reviewing comments in a code change
• Fixing workarounds explained by comments
• Turning documented constraints into automated checks

Collect review feedback and discussion comments from the pull request for the current branch. Get a grouped summary, a prioritized action list, and unresolved questions that need clarification before you proceed.

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

• Prioritizing changes requested in a pull request
• Reviewing feedback scattered across comment threads
• Identifying questions to clarify before making changes

Explore a codebase to explain how a feature or subsystem works, how execution flows, and which files or packages own each responsibility. Build understanding before changes and clarify where new code should belong.

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

• Understanding a feature before changing its code
• Learning the architecture of an unfamiliar subsystem
• Tracing runtime behavior across files or services

Guide debugging from reproducing a failure to finding the first incorrect decision in the code. Distinguish valid states that need handling from invalid states that reveal earlier faults, and look for the same defect elsewhere.

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

• Tracing a failure to its root cause
• Reviewing whether a guard hides a bug
• Investigating failures after a restart

Turn substantial editing, migration, analysis, or verification work into a small, reusable tool. Produce a script, generator, or shared agent skill that performs or checks the work and lets reviewers rerun it.

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

• Automating code edits or migrations
• Generating repetitive files consistently
• Making analysis and verification reproducible

Explore a codebase with SocratiCode to locate features, functions, and types. Search by meaning, inspect how files depend on each other, and find relevant database schemas or API specifications before reading selected files.

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

• Locate the code behind a feature
• Understand file dependencies and circular references
• Find database schemas and API specifications

Set up and maintain SocratiCode indexes, which prepare project files for search. Manage file watching, refresh changed content, rebuild dependency graphs, and check infrastructure health when indexing or search results need attention.

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

• Prepare a project for code search
• Configure automatic or manual index updates
• Investigate interrupted indexing or stale results

Turn a completed workflow or conversation into a reusable agent skill. Clarify inputs, outputs, dependencies, and error handling, then produce an approved design, written instructions or helper scripts, and validation based on the original process.

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

• Packaging a completed workflow as a reusable skill
• Standardizing recurring tasks and error handling
• Combining existing skills into a shared procedure

Prepare the Python package manager uv for skills that depend on it. This skill checks for an existing installation, installs uv if needed, and configures the command search path so uv commands are available.

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

• Preparing to run a skill that requires uv
• Installing uv when it is missing
• Making an installed uv command available

Check maintainer documentation locally before automated CI checks run. Find missing metadata, outdated review dates, nonexistent paths in the architecture manifest, and completed plans that still contain unfinished tasks, with guidance for correcting common failures.

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

• Check required metadata after updating standards
• Find outdated review dates
• Verify paths listed in the architecture manifest

Check whether a pull request is ready to merge by combining local lint, formatting, and tests with GitHub Actions status and PR description requirements. Returns a readiness verdict with specific reasons for any failed checks.

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

• Running local checks before opening a pull request
• Reviewing an existing pull request’s merge readiness
• Finding failing or pending GitHub Actions checks

Fill missing interface translations in a viewer JSON file using English and Chinese source strings. Preview missing entries, translate into six languages through OpenRouter, and validate the updated file with JSON checks and tests.

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

• Adding six-language translations for new interface text
• Previewing missing translation keys before editing
• Retranslating selected entries after source changes

Compare project documentation with code to find outdated descriptions, missing details, and inconsistent references. Review recent changes, audit all documentation, or focus on one area, then apply approved fixes while preserving the existing language and style.

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

• Review documentation affected by code changes
• Audit all documentation against the current code
• Check API or database documentation

Process GitHub issues from selection through code fixes and pull requests, which propose changes for review. Parallel agents implement and test fixes, while review monitoring handles follow-up comments. Filters, fork support, and recurring checks help organize the work.

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

• Fixing a batch of issues labeled as bugs
• Submitting fixes from a fork
• Handling review comments on fix pull requests

Collect, list, and count actionable comments from CodeRabbit and Codex on GitHub pull requests. Separate comments attached to code from review summaries, check Codex status signals, and manage CodeRabbit review conversations.

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

• List actionable comments on a pull request
• Count CodeRabbit comments without minor suggestions
• Check whether Codex is still reviewing

Delegate feature development, code refactoring, and pull request reviews to Codex, Claude Code, Pi, or OpenCode. It guides background execution, progress monitoring, and parallel work in separate working directories.

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

• Delegating new feature or app development
• Reviewing pull requests in a separate working directory
• Refactoring a large codebase

Use the ClawHub command-line tool to find and install agent skills, update them to the latest or a specified version, list installed skills, and publish skill folders with version numbers and change notes.

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

• Find and install a skill for a task
• Install or update a skill to a specific version
• Update all installed skills

Generate a Claude CLI prompt from a structured JSON skill idea. The prompt guides creation of a complete skill directory, including SKILL.md, reference documents, helper scripts, and test scaffolding that follows repository conventions.

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

• Turn a JSON skill idea into a creation prompt
• Prepare prompts for an automated skill generation pipeline
• Include repository structure and quality criteria in skill design

Extract skill ideas from recent Claude Code session logs using repeated actions, errors, and automation requests as signals. Remove duplicates, score novelty, feasibility, and trading value, then maintain a prioritized backlog for skill generation.

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

• Find skill ideas in the past week’s coding sessions
• Identify automation opportunities from repeated actions and errors
• Deduplicate and prioritize skill ideas

Turn an existing conversation and knowledge of the codebase into a specification, then publish it to the project's issue tracker. It organizes the problem, user stories, implementation and testing decisions, and scope without a new requirements interview.

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

• Turning a feature discussion into a specification
• Recording implementation and testing decisions
• Clarifying what is outside the agreed scope

Turn a plan, specification, or conversation into small development tickets that each deliver a verifiable feature. Identify prerequisite tickets, review the breakdown with the user, and publish approved tickets as local files or tracker issues.

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

• Turn a specification into actionable development tickets
• Clarify ticket dependencies and execution order
• Plan a staged refactor across a codebase