2.8K skills · sorted by relevance
Query GitHub issues and extract or summarize selected fields using jq, a JSON filtering tool. Inspect data structure and size before retrieving detailed results, then filter by status, author, labels, comments, or creation date.
Develop user-visible improvements for cc-wf-studio, verify their basis in the code, and assess their value. Record qualifying proposals as locked GitHub issues, creating a queue of concrete ideas for later implementation without changing code.
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
The English summary is being prepared. Showing the original description.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
The English summary is being prepared. Showing the original description.
Triage application logs, open GitHub issues, pending feedback, in-app Issues, and agent conversations. Runs five phases: logs → close shipped issues → feedback → in-app issues → agent FAQ gaps. Use when /whats shows pending feedback, checking app logs, cleaning up shipped issues, or working the in-app Issues backlog.
The English summary is being prepared. Showing the original description.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
The English summary is being prepared. Showing the original description.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Review a set of GitHub issues against their full discussions and current code. Produce a table separating completed work, small fixes, design work, and deferred items, with evidence, confidence levels, and next actions for each issue.
Organize GitHub issues by reading their full descriptions and adding labels for type, effort, priority, and affected area. Preserve existing labels, fill missing categories, and summarize the reasoning alongside duplicate, related, or blocking issue relationships.
Organize Linear or Jira backlogs through the Composio CLI, a command-line tool. Fetch issues in bulk, group likely duplicates, update labels, priorities, and owners, then share a summary of changes in Slack.
Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.
Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
The English summary is being prepared. Showing the original description.
Manages Linear issues, teams, and projects via CLI. Lists issues, creates tasks, views details, links issues, and runs GraphQL queries. Must use for "my Linear issues", "create Linear task", "link issues in Linear", "Linear API query", or any Linear project management request.
The English summary is being prepared. Showing the original description.
Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available. Not for browsing the existing issue tracker. Use oss-find-issue for that.
The English summary is being prepared. Showing the original description.
PRD 到研发 Issue 拆解 / implementation issues：当用户已有 PRD、需求文档、handoff、产品方案或 GitHub PRD issue， 需要拆成可独立领取、可验收、适合 GitHub Issues 承接的开发任务时使用。可用中文唤起： “把 PRD 拆成 issue”“需求文档拆任务”“生成 GitHub issues”“PRD 拆工单”“拆 implementation issues” “按 vertical slice 拆开发票”。不用于从零写 PRD；那类请求用 prd-architect。不用于评审 PRD 是否完整； 那类请求先用 prd-review。
The English summary is being prepared. Showing the original description.
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
The English summary is being prepared. Showing the original description.
Investigate duplicate OpenClaw pull requests and issues using local history and current GitHub evidence. Organize confirmed or suspected duplicates in prtags, recording the decision, confidence, and reasons for maintainers.
Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.
Organize GitHub issues, synchronize project boards, and plan sprints, or short work cycles. Coordinate multiple AI agents to break issues into tasks, assign work, update progress, and track dependencies across a project.
Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.
Manage work on a SeaClip-Lite project board through commands that create and update issues, control pipelines, configure schedules, and inspect recent activity, with JSON output for AI agents.
Check web pages and components for accessibility issues against WCAG 2.2, web accessibility guidelines. Receive a report prioritized by user impact, or request targeted code fixes followed by verification of resolved and newly introduced issues.
Review open GitHub pull requests and issues to rank useful, lower-risk actions. Produce a prioritized report covering merge candidates, already-fixed issues, small fixes, branch verification, and contributor credit, with public comments drafted for approval.