스킬 찾기

Prepare Cline CLI releases for npm, the package registry, by reviewing SDK changes, drafting release notes, updating versions and changelogs, and creating release tags. Guides checks and publication through GitHub Actions or an authenticated local machine.

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

• Drafting CLI release notes from relevant changes
• Updating the CLI version and changelog
• Publishing a tagged release through GitHub Actions

Prepare Cline desktop releases for stable, beta, or nightly testing. Coordinate release notes, matching version files, tags, and a GitHub Actions workflow that builds signed installers and manages automatic update feeds for release channels.

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

• Preparing a stable desktop release
• Publishing a beta alongside the stable app
• Creating signed nightly test installers

Prepare and publish standalone @cline/ui releases to npm, the package registry. Covers version updates, quality checks, production and preview channels, release verification, and the initial setup that lets GitHub Actions publish the package.

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

• Preparing a production UI package release
• Publishing a preview with an explicit prerelease version
• Checking tests and package contents before release

Investigate LazyCodex and Codex bugs using reproduction results and source code. Identify the responsible repository, then prepare or submit an English GitHub report with evidence, likely causes, fix guidance, and a verification plan.

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

• Report a reproducible LazyCodex or Codex bug
• Identify which project owns a defect
• Add new evidence to an existing issue

Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.

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

• Reviewing a backlog of open issues and pull requests
• Checking whether reported bugs are already fixed
• Assessing pull request readiness for merging

Checks LazyCodex and Codex CLI installations against current source code, inspecting versions, settings, plugin files, and runtime behavior. Produces an evidence-backed health report with suggested fixes while leaving the installed setup unchanged.

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

• Diagnosing unexpected behavior after an update
• Checking configuration and plugin files
• Auditing differences from current source code

Publishes oh-my-opencode through GitHub Actions, then checks package versions and release artifacts. Covers related packages, user-facing release summaries, and Discord announcements, reporting failures without starting code repairs during the release process.

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

• Publishing a patch, minor, or major release
• Releasing a specific prerelease version
• Checking related packages and platform binaries

Take implementation work through small, independently mergeable pull requests. Use a separate working directory for each PR, record manual QA evidence, write English review descriptions, resolve CI and review findings, then merge and clean up.

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

• Deliver implementation work through pull requests
• Split a large task into small, independently mergeable PRs
• Build independent PRs concurrently

Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.

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

• Implement and verify a reproducible bug fix
• Submit an upstream Codex pull request
• Deliver a tested LazyCodex patch in an issue

Reviews completed changes through hands-on checks and one reviewer agent. It compares the implementation and recorded evidence with the original goal, constraints, code quality, and security requirements, then reports approval, specific blockers, or an inconclusive result.

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

• Reviewing completed changes before a pull request handoff
• Checking whether an implementation meets the original request
• Organizing failed checks and required fixes

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

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

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Search and work with GitHub repositories through GitHub’s official MCP server, which connects agents to available tools. The skill guides account authorization, repository access selection, and tool use, with separate controls for reading and making changes.

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

• Search repositories available to the connected account
• Choose which repositories the app may access
• Check why a repository is unavailable

Inspect a codebase and create concise project instructions for Claude Code. Review existing guidance, separate team rules from personal preferences, and propose reusable skills or hooks that run commands automatically.

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

• Set up project instructions for Claude Code
• Review and improve an existing CLAUDE.md
• Separate personal preferences from team rules

Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.

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

• Review uncommitted changes for bugs
• Check a pull request or branch before merging
• Find duplicated logic and unnecessary work

Audit a Claude Code setup for installation problems, broken settings, unused extensions, and duplicated instructions. It reviews local usage evidence, recommends cleanup, and applies approved fixes, with separate confirmation for permission changes.

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

• Diagnose installation and configuration problems
• Review unused skills, MCP servers, and plugins
• Trim duplicated or unnecessary CLAUDE.md guidance

Review recent Claude Code session logs to find frequently used read-only Bash commands and MCP tools, which connect agents to services. Rank suitable permission rules and merge them into project settings to reduce repeated approval prompts.

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

• Reduce prompts for frequently used read-only tools
• Choose permission rules from actual usage
• Add project rules while preserving existing settings

Turn a website's screenshots and brand assets into a HyperFrames site tour or social clip. Develop a storyboard and script, add optional narration and captions, then validate the video and deliver a Studio preview.

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

• Creating a video tour of a portfolio
• Turning a blog or landing page into a social clip
• Making a site showcase with narration and captions

Monitor a GitHub pull request for review feedback, automated check failures, and merge readiness. Diagnose failures, fix problems caused by the branch, and retry likely temporary failures while continuing to watch for updates.

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

• Monitor automated checks after opening a pull request
• Address actionable review feedback
• Distinguish code failures from temporary service problems

Find and install Codex skills from a curated catalog or a GitHub path. Check which skills are already installed, explore experimental options, and add skills from private repositories when credentials are available.

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

• Browse available skills and check installed ones
• Install a skill by name from the curated catalog
• Add a skill from a private GitHub repository

Start video and animation work by matching the request and project state to an appropriate HyperFrames workflow. It coordinates new productions, edits, captions, previews, validation, and rendering, using HTML files to define the video.

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

• Create a product video from a website or brief
• Add captions or graphic overlays to existing footage
• Resume editing an existing HyperFrames project

Turn a GitHub pull request into a video explaining a feature, fix, refactor, or changelog. The workflow uses actual diffs, commits, and files to plan the story, show code excerpts, and produce an MP4.

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

• Explain a new feature from its pull request
• Show the code changes behind a bug fix
• Walk through a refactor with actual excerpts

Refresh the GitHub star count displayed on Remotion’s website. It checks GitHub, rounds the number down to the nearest thousand, updates three components, and commits and pushes the changes to main.

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

• Refreshing the homepage’s GitHub star display
• Updating star counts across three website components
• Committing and pushing the display update to main

Prepare current changes for a GitHub pull request by formatting affected files, checking builds and style, committing, and pushing. Create or update the PR, link related issues, and add page previews when available.

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

• Opening a pull request for the current feature
• Updating an existing PR with local changes
• Formatting changes and checking builds before submission

Investigate intermittent Remotion CI failures, record their error patterns in a tracking issue, and increment counts for repeated failures. Find failed checks even without a supplied pull request, then rerun affected GitHub Actions jobs.

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

• Investigate a CI failure that may pass on retry
• Find failed checks without a pull request number
• Record recurring failures and update their counts