bug-triage
Triage open GitHub bug issues for Apify MCP server. Fetches issues, analyzes root causes, drafts developer-to-developer responses, and posts after user approval. Use when handling user bug reports, responding to issues, or cleaning up stale bugs.
Install
With your agent
Install OMGSkills skill "apify/apify-mcp-server:bug-triage" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/apify/apify-mcp-server /tmp/apify-mcp-server && ln -s /tmp/apify-mcp-server/.claude/skills/bug-triage ~/.claude/skills/bug-triageFrom README
Bug Triage Triage open bug issues on apify/apify-mcp-server. Analyze, draft responses, get approval, post. Permissions Read-only by default: listing issues (gh issue list), viewing details and comments (gh issue view) — do these automatically, no need to ask. Write requires approval: commenting (gh issue comment), closing (gh issue close), editing (gh issue edit) — always present the draft and wait for explicit user approval before executing. Step 0: Parse arguments $ARGUMENTS controls scope: | Input | Behavior | |---|---| | 623 641 639 | Triage specific issue numbers | | --label bug | Triage all open issues with label (default: bug) | | --all | Triage all open bug-labeled issues | | (empty) | Same as --all | Step 1: Fetch issues Use the arguments parsed in Step 0 to determine what to fetch. If specific issue numbers were provided, skip the list queries and fetch each issue directly: Otherwise (label mode, --all, or empty), fetch open bug reports.