Automate GitHub issue triage and pull request creation via sub-agents.
npx skills add https://github.com/aayushsoam/clawbot-plus --skill gh-issues-aayushsoam
Please help me install this Agent Skill. Skill: gh-issues Source: https://github.com/aayushsoam/clawbot-plus/tree/main/skills/gh-issues Command: npx skills add https://github.com/aayushsoam/clawbot-plus --skill gh-issues-aayushsoam
GitHub issue management typically involves repetitive triage, manual assignment, and back-and-forth between issues and PRs. This Skill orchestrates the process by fetching issues, spawning deterministic sub-agents to implement fixes, and opening pull requests, all while monitoring reviews and coordinating fork workflows.
Invoke /gh-issues with an owner/repo and optional flags to auto-fetch issues, spawn fix agents, and open PRs.
High-intent search queries and answers about installing and using this skill.
Automate GitHub issue triage by fetching labeled issues and spawning sub-agents to implement fixes, which then automatically open pull requests. This orchestrates the entire workflow from token resolution and issue retrieval to fork handling and PR review monitoring.
Yes, you can use sub-agents to automatically create PRs for fork-based GitHub repositories. The automation handles fork workflows and token-based authentication to spawn agents that implement fixes and submit pull requests.
Sub-agent orchestration for GitHub issue fixes works by spawning parallel deterministic agents to implement code changes based on retrieved issues. It coordinates multi-phase processing, optional model selection, and notification channels while monitoring PR reviews.
The best way to monitor GitHub issues for new activity and assign milestones is using watch mode for continuous operation. It fetches issues by labels, milestones, and assignees, tracking updates to trigger automated sub-agent fixes.
Yes, GitHub issue automation supports cron mode for scheduled, cron-safe processing of maintenance projects. This allows continuous operation alongside watch mode, with optional model selection and notify-channel configurations.
Yes, you need a GitHub token to automate issue fixes and open pull requests. The process requires token-based authentication for issue retrieval, fork handling, and PR creation within the multi-phase orchestration workflow.
borealBytesAutomate GitHub issue triage, fix agent spawning, and PR creation via parallel sub-agents.
pablomat555Fetch GitHub issues and orchestrate sub-agents to implement fixes and create PRs.
Z1-TestAutomate GitHub Issues creation, updates, milestones, and sub-issues via REST API.
191854169Fetch GitHub issues and spawn parallel sub-agents to implement fixes and open PRs.
