2.9K skills · sorted by relevance
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".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Label unlabeled GitHub issues with priority and type labels. Use when triaging issues, cleaning up the backlog, or when asked to label/triage issues.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。
The English summary is being prepared. Showing the original description.
Use when the user, inside an Orca terminal, asks Hermes to resolve, dispatch, orchestrate or supervise GitHub issues with Orca workers — 'orquestrar as issues 12, 15 e 18 no Orca', 'despachar as issues com label ready', 'coordenar workers do Orca para estas issues', or to resume such a Run after compaction. Do NOT use for a single unsupervised hand-off to another agent (Orca CLI directly), for working on one issue in this session (pwdev-feat feat-loop), or outside Orca.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.
The English summary is being prepared. Showing the original description.
Coordinate repairs across multiple OpenClaw issues or pull requests, which propose code changes. Assign owners, prove defects, verify fixes, and track outcomes through merging or closing resolved items within the authorized scope.
Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.
Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.
Sort issues and external pull requests, which are proposed code changes, by category and readiness. Verify reports, identify missing information, and record clear briefs so an agent or a person can take the next step.
Triage GitHub issues and pull requests, classify their next steps, and connect active work to Linear. Keeps public updates in GitHub and internal ownership and priorities in Linear, with a clear recommendation for the next action.
Manage GitHub repository operations with the gh command-line tool. Classify issues, check pull request readiness, investigate failed automated checks, prepare releases and changelogs, and review dependency or exposed-secret security alerts.
Retrieve Jira issues, turn their requirements into testable criteria, and keep progress updated within an AI coding workflow. Includes issue searches, comments, and status changes through MCP tools or direct REST API calls.
Manage GitHub work with the gh command-line tool, from issues and pull requests, which propose code changes, to reviews and repository management. Follow task-specific workflows and verify checks, merges, and other remote states.
Summarize the past 24 hours of GitHub pull requests, review requests, issues, CI runs, and merges in a daily briefing. The GitHub-style page highlights pending reviews and failed automated checks.
Build an HTML dashboard for a public GitHub repository, showing stars, forks, contributors, issues, pull requests, and recent activity. Choose a standalone page or source files that support updates and record where the data came from.
Manage GitHub issues, synchronize project boards, and plan sprints, short development cycles. Coordinate multiple AI agents to break work into tasks, assign responsibilities, update progress, and produce reports on completion and blockers.