2.8천건 · 관련도순
Manage Linear issues and projects through natural-language requests. Review priorities, create and update tickets, inspect team workloads, and organize release plans using a workflow that reads existing information before making changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review OpenShell issues, pull requests, and failed main-branch checks, then build a local Markdown report with linked evidence and ranked recommendations. Saved progress helps resume an unfinished triage pass without changing GitHub.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check whether OpenShell issues and pull requests fit the project, then track review feedback and automated checks. State labels show what needs attention and when a pull request is ready for maintainer approval or a merge decision.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues + agent:implement multi-session workflow. Argument is the parent PRD issue number.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues. Not for finding problems that nobody has filed an issue for yet. Use oss-find-real-issues for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when filing one or more GitHub issues for planned work — "file an issue for this", "turn this plan into issues", "open a tracking issue". Covers filing everything on skyf0xx/hedgehog regardless of which repo's code changes, whether to split a plan into a tracking issue plus sub-issues, which account files the issue, labels, and acceptance criteria. For how to word an issue, see the pr-writing skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open GitHub Issues for human input and respond to the researcher team. Use this skill whenever you need to handle a human_issue event, respond to human issues, ask humans a question, or check team communications. Also triggers for: "any human messages?", "check issues", "respond to humans".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Label unlabeled GitHub issues with priority and type labels. Use when triaging issues, cleaning up the backlog, or when asked to label/triage issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to clean up fingerprint sprawl. Decides between a one-shot merge of existing issues and a durable grouping rule that keeps future events from creating new fingerprints. Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use quando um roadmap pwdev-roadmap/1 (roadmap.json) precisar ir para o GitHub — 'publicar o roadmap', 'criar as issues do roadmap', 'publish roadmap.json' — com issues, sub-issues, milestones, blocked-by e campos do Project, com dry-run, idempotente e retomável. Não use para uma issue avulsa (github-issues).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.