'github' 검색 결과

Use when the user wants to find or discover a Claude Code skill that is NOT already installed — e.g. "is there a skill for X", "find me a skill that…", "what skills exist for…", or "/find-skill <topic>". Searches the official plugin marketplace, GitHub, and curated awesome-lists for community skills matching a need, removes anything already installed, and recommends the top 5 with links. Do NOT use this to create or edit skills (that is skill authoring), or to pick among skills you already have.

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

Use when creating Product Hunt launch carousel images for developer tools, AI tools, open-source projects, GitHub launches, or technical products. Research comparable launches, inspect the project, extract verified proof points, then generate 4-5 launch-ready images with consistent branding, product surfaces, readable copy, and source-grounded claims.

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

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by answer-issue-questions and breakdown-issues. It formats a scope GitHub Issue body (label cc-triage-scope, used before code analysis), runs the pre-posting checklist, and executes `gh issue create`. Invoke this skill ONLY from one of the parent skills via the Skill tool, after the parent has finalized the task breakdown. If a user asks to 'create a scope issue' or similar, route them to the appropriate parent skill (/breakdown-issues for fresh breakdowns, /answer-issue-questions for derived sub-tasks) rather than invoking this one directly.

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

Re-analyze an existing GitHub Issue using its current title and body as input, refresh the implementation plan against the latest code state, and update the Issue in place. Use this when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the Explore-based analysis. For reflecting comment-driven updates instead, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

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

Triage a single GitHub PR by PR number. Check out the PR's branch, detect conflicts with the target branch via `gh pr status` (and label the PR with `cc-resolve-conflict` if any are found), generate and evaluate a fix plan via create-review-fix-plan, then take action (add cc-fix-onetime label if fixes are needed, or merge the PR if it's ready).

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

Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.

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

Triage a GitHub issue that already has the cc-issue-created label and is assumed to be ready to start. First inspect the comment history to decide whether human confirmation is needed (cc-need-human-check, highest priority); otherwise decide whether the issue should be closed as not needed, unanswered confirmation items remain (cc-answer-issue-questions), the description is stale relative to settled comment-history content and must be refreshed before execution (cc-update-issue), or it can move to execution (cc-exec-issue). Dependency checks are out of scope.

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

Execute tasks based on GitHub Issue content

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

Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.

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

架构设计前系统搜索开源底座（GitHub/包注册表/Awesome/Web），输出 ADOPT/FORK_BASE/COMPOSE/REFERENCE/GREENFIELD 决策与改造蓝图。不用于市场调研或找单个依赖库。

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

Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.

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

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

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

Manage Agent Skills across Codex, Claude Code, local/global/project roots, Skill Hubs, GitHub, skills.sh, and managed plugin caches. Use when searching, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, validating, resolving upstream sources, choosing runtime or scope, or working with skill-upgrade, check_upstreams.ps1, Claude Code plugins, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.

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

Review a GitHub pull request and provide structured feedback with severity ratings

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

Fix a GitHub issue by reading the issue, finding relevant code, implementing a fix, and creating a commit

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

Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or parallelizable task breakdown.

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

自动搜索、抓取、改写技术内容，生成适合微信公众号的中文科普文章。涵盖AI大模型、GitHub开源工具、技术话题。当用户说"写一篇关于XXX的文章"、"帮我研究XXX"、"生成公众号文章"时使用。

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

You are a senior engineering lead and product architect. Given an observation, bug, or gap, conduct a thorough multi-dimensional investigation, find the root cause, plan the resolution, and create a detailed actionable GitHub issue.

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

Create a GitHub Pull Request with full AI review. Human approves and merges.

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

Sync 7 days of GitHub activity (commits, PRs, issues, reviews) into a structured context dump. Optionally pull from Slack, GDrive, or Asana if configured. Use at the start of a session to get fully caught up before coding.

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

Use this skill when someone wants to contribute, submit or publish a GRC skill to the grcskills library (github.com/better-isms/grcskills, grcskills.com), or update a skill or author profile they already published there. Interviews the contributor for practitioner judgment, drafts the files in the library format, runs the validator and opens one pull request.

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

Migrate legacy spec sources to artifact-first GitHub Issue specs. Supports local `specs/SPEC-*` directories and body-canonical `gwt-spec` Issues using the bundled migration script.

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