Processes GitHub issues sequentially with dependency ordering and CI-gated PR merges.
npx skills add https://github.com/rioX432/live-translate --skill dev-all
Please help me install this Agent Skill. Skill: dev-all Source: https://github.com/rioX432/live-translate/tree/main/.claude/skills/dev-all Command: npx skills add https://github.com/rioX432/live-translate --skill dev-all
This Skill streamlines sequential GitHub issue delivery by organizing related work into isolated per-issue branches, validating each change, and merging only after checks pass.
Use the dev-all skill to process the selected GitHub issues sequentially, wait for CI after each pull request, and merge them in order.
High-intent search queries and answers about installing and using this skill.
Batch resolving GitHub issues into separate pull requests requires organizing related work into isolated per-issue branches, validating each change with CI, and merging sequentially only after checks pass. This approach keeps changes atomic and easy to review.
Dependency-aware sorting for multi-issue development batches detects blocked-by relationships among GitHub issues and orders work topologically. This prevents rework and merge conflicts by ensuring prerequisite issues are resolved before dependent ones are addressed.
Automating pull request merges after CI checks pass involves waiting for continuous integration validation, evaluating review outcomes, and deciding whether to merge, skip, or continue. This CI-gated merge flow ensures only validated changes are merged.
Processing a backlog of GitHub issues in one session without mixing changes requires sequential issue processing across isolated worktrees. Each issue gets its own branch, keeping changes atomic and maintaining clear validation status throughout the batch.
When CI validation fails during automated GitHub issue resolution, the flow applies failure handling for warnings, CI errors, and skipped items. It evaluates the outcome and decides whether to retry, skip the item, or continue to the next issue.
Isolated Git worktrees are required to manage sequential GitHub pull requests because they provide per-issue investigation environments and separate branches. This isolation ensures dependency ordering and autonomous execution do not cause merge conflicts.
kynopticManage GitHub issue blocking relationships via GraphQL mutations and queries.
JordiNodeJSAutomate GitHub pull request creation, updates, merging, and release tagging via GitHub CLI.
BaqiF2Merge GitHub Pull Requests after CI checks and code review pass.
aroidoLock a GitHub issue, prevent duplicate PRs, and create a branch.
