스킬 찾기

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

Organize GitHub issues using parent and child relationships and links showing which tasks must finish first. Use gh CLI to create, change, remove, and inspect relationships, including links across repositories.

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

• Breaking a large issue into linked sub-issues
• Recording which issues must be completed first
• Linking dependent issues across repositories

Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.

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

• Finding open issues outside a masterplan
• Distinguishing missing parents from missing plan ancestors
• Checking issue organization in automation

Create and edit Remotion GitHub issues, add comments, and attach images or videos. It keeps titles aligned with the user’s intent and checks saved issue text to ensure Markdown formatting and line breaks are preserved.

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

• Creating a Remotion bug report
• Editing an existing issue’s title or body
• Adding comments with screenshots or videos

Organize dependent changes into a chain of branches and pull requests so reviewers can inspect one layer at a time. Use the GitHub CLI extension to create, update, synchronize, and merge the chain.

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

• Splitting a large change into reviewable pull requests
• Updating a lower branch and rebasing dependent branches
• Synchronizing local branches with GitHub

Research recent discussions about a topic across social platforms, communities, and the web. Collect posts and engagement from the last 30 days, summarize supported findings with source links, and diagnose unavailable or broken research sources.

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

• Reviewing reactions to a product or announcement
• Comparing recent user opinions about tools
• Finding topics gaining attention in a field

Maintain a Chinese independent developer project list by reviewing comments, issues, and pull requests. Check duplicate URLs and submission eligibility, add projects to the appropriate README, merge contributions, and reply with the listing result.

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

• Review new project submissions
• Check duplicate product URLs
• Place projects in the appropriate list

Organize open pull requests before a release, classify what to merge or defer, and track decisions in a resumable document. Guide review, merging, follow-up fixes, and closing requests already covered by other changes.

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

• Sort a backlog of pull requests before a release
• Prioritize bug fixes for the next version
• Resume interrupted reviews from a progress document

Manage scientific datasets with DataLad and git-annex, which tracks large files separately from Git history. Retrieve selected data, record analysis commands and their inputs and outputs, rerun recorded work, and publish history alongside file content.

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

• Retrieve only the research data you need
• Resolve files that contain pointers instead of data
• Record and rerun analysis steps

Manage dependent branches and pull requests with the GitHub gh-stack extension. Plan their order, inspect relationships, propagate changes through higher branches, and handle synchronization or conflict recovery using the documented workflow.

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

• Plan dependent changes across multiple pull requests
• Propagate lower-branch fixes through dependent branches
• Inspect and link existing pull requests

Create or update GitHub pull requests using the project's required template. Organize changes and test results, preserve every template section, and check target branches and release notes against the documented workflow.

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

• Create a pull request using the required template
• Organize changes and test results for a draft pull request
• Check hotfix and backport requirements

Delegate repository analysis and coding tasks to GitHub Copilot CLI without an interactive session. The skill reads structured output, checks errors, and summarizes the final result along with any denied tool requests.

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

• Ask Copilot to explain a failing test
• Delegate repository analysis to Copilot
• Request code changes with narrowly scoped tool permissions

Create GitHub issues that follow the current repository's templates. The skill selects the appropriate report format, collects required information, and prepares the title, body, labels, and issue type for review before submission.

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

• File a bug report using the repository's template
• Submit a feature request with required details
• Create an internal engineering task as a maintainer

Analyze a project’s code and existing settings to recommend useful Claude Code automations. Receive tailored suggestions for event-triggered actions, specialist agents, skills, plugins, and external tool connections, with reasons and setup locations.

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

• Choosing Claude Code features for a new project
• Finding ways to automate formatting and checks
• Selecting external tool connections for the project

Prepare a Cherry Studio release by checking changes against the published version, writing English and Chinese release notes, updating version metadata, and creating a release branch after review to start the build workflow.

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

• Preparing a patch, minor, or major release
• Preparing a beta or release candidate
• Writing release notes from final user-visible changes

Reviews Cherry Studio code and documentation against product decisions, architecture rules, implementation checks, and conventions. It selects a review approach based on scope and available agents, then reports findings with guidance for fixes.

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

• Reviewing local changes or a branch
• Checking a pull request before merging
• Reviewing architecture documents and project skills

Prepare and submit bug reports or feature requests to GitHub, checking for duplicates and following issue templates. Reports are previewed for approval before submission, or saved locally when GitHub authentication is unavailable.

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

• Report a bug to GitHub with clear reproduction steps
• Prepare a feature request using the issue template
• Save reports locally when GitHub login is unavailable

Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.

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

• Checking key workflows before a release
• Validating application behavior on a development branch
• Running regression tests for a specific task

Turn a Cherry Studio support conversation into an editable draft for a bug report, usability issue, or feature request. The user reviews the wording, chooses any diagnostic data, and submits the report themselves.

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

• Draft a bug report from a support conversation
• Organize feedback about interface usability
• Prepare a feature request for review

Investigate a GitHub issue or reported problem, check whether it is a bug, and test a proof of concept. Explain the behavior changes and supporting evidence so the user can decide whether to proceed with the full fix.

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

• Checking whether a reported issue is a real bug
• Testing a proposed fix before full implementation
• Comparing performance before and after a change

Take a pull request through repeated code review and fixes, verify that automated checks pass for the latest commit, and combine its changes into one commit when merging. Conflicts with the request’s goal require confirmation.

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

• Reviewing, fixing, and merging a pull request
• Resolving every review finding, including minor issues
• Checking CI results for the commit being merged

Prepare and publish a core Hindsight release, then open a pull request for its changelog and announcement blog post. Covers version updates, package publication checks, and synchronization of the accompanying documentation references.

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

• Publishing a new core Hindsight version
• Preparing a release changelog and announcement
• Checking release tags and publication workflows

Create an animated diagram showing request flows, background jobs, or feature changes. The result is a single SVG image for README files, pull requests, issues, or blog posts, with support for light and dark themes.

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

• Explaining request and data flows
• Illustrating how a background job works
• Showing feature changes in a pull request