개발 스킬

Build and maintain TypeScript MCP servers that connect AI to tools, plus interactive MCP Apps, using mcp-use. The skill guides implementation, authentication, migration, and verification based on the package version and types installed in the project.

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

• Starting a TypeScript MCP server project
• Adding interactive Views to MCP Apps
• Reviewing OAuth authentication and permissions

Turn an OpenAPI or Swagger specification into an MCP server, a bridge that lets AI assistants call an API. Covers tool generation, authentication, local testing, and deployment to mcp-use cloud.

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

• Make an internal API callable from Claude
• Generate MCP tools from a Swagger specification
• Test API calls locally before cloud deployment

Build and maintain TypeScript MCP servers that connect AI to tools, plus interactive MCP Apps, using mcp-use. The skill guides implementation, authentication, migration, and verification based on the package version and types installed in the project.

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

• Starting a TypeScript MCP server project
• Adding interactive Views to MCP Apps
• Reviewing OAuth authentication and permissions

Build and maintain TypeScript MCP servers and MCP Apps with mcp-use, giving AI assistants tools and interactive views. Guides implementation, authentication, debugging, migration, review, and verification against the package version installed in the project.

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

• Build an MCP server with tools and prompts
• Add interactive React views to an MCP App
• Migrate existing code to the installed mcp-use version

Learn how to organize an AI agent skill using a sample SKILL.md file. It covers basic metadata, procedural instructions, supporting folders, and relative paths, and serves as an example for testing the OpenSkills loader.

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

• Learning the basic structure of an agent skill
• Drafting a SKILL.md file
• Organizing references, scripts, and templates

Find where code lives, understand how it works, and trace connections between functions using a repository index. Results include file locations and line numbers to help plan edits and assess which other code a change could affect.

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

• Understanding an unfamiliar codebase
• Finding where a behavior is implemented
• Checking the impact of renaming a function

Compare the installed Claude Code version with release notes and recent bug reports to decide whether to stay, update, or use a specific version. Recommendations account for reported problems, relevant fixes, and how Claude Code was installed.

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

• Deciding whether to update Claude Code
• Checking reports of problems in a recent release
• Choosing a version to roll back to

Review recent conversation history against global and project CLAUDE.md files, which hold agent instructions. Identify rules that were missed, useful additions, and outdated guidance, then organize findings into shared and project-specific improvements.

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

• Reviewing instructions after repeated corrections
• Adding project-specific working rules
• Separating shared rules from project guidance

Search across public and private GitHub repositories using local copies and ripgrep, a text search tool. Find which repository or file contains an implementation, phrase, or setting, with results drawn from the default branch.

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

• Find which repository contains an implementation
• Locate configuration files across repositories
• Search private repositories for a phrase

Edit and validate Bazel build settings using conventions specific to CodeQL development. Follow established helpers for packaging and operating system differences, add dependencies with checksums, and check changed targets while respecting the standalone build setup.

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

• Edit CodeQL Bazel build files
• Configure packaging for different operating systems
• Add external build dependencies

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

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

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Run a quick first review of code changes with six specialist agents working in parallel. They check logic, input and output, shared state, resources, missing behavior, and API completeness, then combine duplicate findings into a report ranked by confidence.

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

• Running a quick first review of a patch
• Screening diffs to prioritize further investigation
• Checking for missing cleanup and handlers

Explain code structure and behavior with text diagrams, including before-and-after views of changes. Trace data flow and state changes, clarify design choices, and examine assumptions, possible failures, and interactions between tasks running at the same time.

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

• Understanding a patch through before-and-after diagrams
• Tracing a class's behavior and state changes
• Mapping component relationships across a codebase

Review changes of 1,000 lines or more by dividing work across files, focused areas, and commits. Combine several review methods, check consistency across subsystems, verify bug fixes, and report validated findings alongside a checklist showing review coverage.

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

• Reviewing feature branches with 1,000 or more changed lines
• Checking a large change before merging
• Finding inconsistencies across commits and subsystems

Analyze Git history to find frequently and recently changed files and lines, then rank review targets. Use the results to focus pull request reviews, bug investigations, or security audits on specific code regions and risks.

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

• Prioritizing files during pull request reviews
• Finding starting points for bug investigations
• Narrowing security audits to frequently changed code

Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.

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

• Review selected files in a critical code change
• Investigate concerns raised by an initial review
• Check complex state transitions and object lifecycles

Analyze bug-fix commits in a Git repository to uncover recurring failure patterns. Produce individual bug analyses and a reusable pattern guide that removes project-specific details, helping inform future code reviews.

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

• Extract recurring bug patterns from past fixes
• Build a reusable guide for code reviews
• Analyze fixes within a chosen date range or path

Build React and TypeScript pages with guidance for data fetching, loading states, styling, and navigation. Organize code by feature and apply lazy loading, which loads components when needed, using patterns for MUI v7 and TanStack Router/Query.

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

• Creating a React page or component
• Organizing frontend files by feature
• Coordinating data fetching and loading states

Create and maintain Claude Code skills with clear file structure and activation rules. Get guidance on hooks, which run at specific workflow events, plus troubleshooting, edit restrictions, and splitting detailed instructions into reference files.

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

• Creating a new Claude Code skill
• Tuning skill activation conditions
• Investigating missing or unwanted activation

Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.

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

• Adding an API endpoint
• Separating business logic from database access
• Standardizing input validation and error handling

Find where code lives, understand how it works, and trace connections between functions using a repository index. Results include file locations and line numbers to help plan edits and assess which other code a change could affect.

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

• Understanding an unfamiliar codebase
• Finding where a behavior is implemented
• Checking the impact of renaming a function

Prepare English pull requests for Apache SeaTunnel from a change summary, branch history, and file differences. It builds titles and bodies that follow project conventions, records actual testing, and can submit the pull request when requested.

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

• Drafting an English PR from current branch changes
• Choosing a PR title that follows SeaTunnel conventions
• Completing the PR template with changes and actual test results

Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.

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

• Review changes in the current working directory
• Review a separate working directory
• Review a pull or merge request by URL

Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.

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

• Review code changes from Kiro
• Review a separate working directory
• Open a review for a pull request URL