4.1K skills · sorted by relevance
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.
Diagnose OpenCLI commands broken by website changes, collect execution traces, patch the adapter that connects to the site, and retry. After a verified repair, prepares a GitHub issue for submission with user approval.
Investigate a GitHub issue or bug report by tracing code, checking relevant history, and testing the diagnosis where needed. Receive a concise verdict, supporting evidence, a proposed fix direction, and a record for follow-up questions.
Draft and post GitHub pull request reviews and issue comments with precise locations, required changes, and supporting reasons. It checks the posting account, applies approval rules, and selects the appropriate review outcome.
Review Qwen Code issues and pull requests through staged checks. Assess product fit, code simplicity, and CI evidence, then prepare English and Chinese comments that explain findings and flag decisions needing maintainer attention.
Manage GitHub collaboration through the gh command-line tool and GitHub APIs. Create and review pull requests, organize issues, investigate failed Actions workflows, check automated tests before merging, and prepare releases with generated notes.
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.
Review an authorized security issue in its private workflow. Check the affected code, assess whether the report is valid, explain severity and attack prerequisites, and propose a remediation plan with focused tests.
Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.
Investigate a Sandcastle GitHub issue, classify the report, check for duplicates or existing fixes, and attempt reproduction with Docker. Return a minimal reproduction script, observed results, and a likely cause, noting any environment limitations.
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.
Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.
Prepare external contributions to gentle-ai through approved issues, accurate pull request descriptions, and plans for splitting large changes. Check claims against test results and GitHub state while respecting contributor and maintainer permissions.
Guides agents to access GitHub repositories, pull requests, issues, and APIs through the authenticated gh command-line tool. Covers private repository access and recommends cloning repositories to read files locally, with commands for viewing GitHub information.
Inspects GitHub repositories, pull requests, issues, reviews, and automated Actions runs through the connected iPolloWork service. Combines remote information with the local checkout, summarizes relevant evidence, and routes review fixes, CI investigation, or publishing to specialist workflows.
Review issues and external pull requests, classify them, verify their claims, and assign a handling state. The skill checks existing implementations and past rejections, requests missing details, and prepares briefs that agents or human maintainers can act on.
Prepare and publish a pull request with a linked issue, English commit and PR titles, and a Chinese description explaining the change, implementation, and verification. Update an existing branch PR and report its URL and CI status.
Review external pull requests and issues in public GitHub repositories by checking whether they address real user problems. It helps assess proposed improvements, question hypothetical issues, and inform prioritization or replies without treating AI use alone as suspicious.
Build an implementation queue from accepted GitHub issues and distribute them to dedicated workers. Record selection reasons, check for existing pull requests, and process the full queue with a configurable concurrency limit, defaulting to two workers.
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.
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".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue properly", or /gaia-issue-resolver. Works any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven — while the issue itself lives on the headquarters tracker, gaia-research/gaia-skill-tree. Assumes the issue is already triaged and carries a P0–P4 label; if it does not, run /gaia-triage first.
The English summary is being prepared. Showing the original description.
依頼された内容を要件とTODOに分解し、タスクごとにGitHub Issueを作成するスキル。タスクの整理・分解、複数Issueの一括作成、依存関係の明示が必要な場合に使用する。「この機能をIssueに分けて」「タスクを洗い出してIssueにして」「要件を整理してチケット化して」といったリクエストで発動する。
The English summary is being prepared. Showing the original description.