dev-hotl

Autonomously selects and executes one prioritized dev pipeline task from GitHub PRs and Issues.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill dev-hotl-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-hotl
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/dev-hotl
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill dev-hotl-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a development pipeline manually requires constantly checking which PRs need review responses, which PRs await review, and which Issues are ready for implementation. This Skill removes that triage burden by autonomously picking the single highest-priority task and executing it end-to-end without asking for human confirmation. ## Core Features & Use Cases - Priority-Based Task Selection: Scans open PRs and Issues in a fixed order (review-comment resolution → PR review → Issue implementation → Issue triage) using GitHub CLI label queries, and locks onto the first match. - Fully Autonomous Execution: Runs with Human Out of The Loop — no confirmation prompts, no needs-info labels; it verifies decisions against the codebase, Issue history, and web search instead. - Resolved-Issue Cleanup: Closes already-resolved Issues it encounters, always with a documented rationale referencing commits, PRs, or file paths. - Use Case: You tell the agent "run the dev pipeline autonomously" before a break; it updates main, finds the oldest PR with unresolved review comments, invokes the corresponding dev skill to resolve and merge it, then reports the outcome. ## Quick Start Tell the agent to run the dev pipeline autonomously and it will update main, pick the highest-priority PR or Issue, and complete one task end-to-end.

Frequently Asked Questions about dev-hotl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PR review and issue triage on GitHub?▼

Use gh CLI label queries to list open PRs and Issues by state, then process them in a fixed priority order. This Skill checks review-comment responses first, then unreviewed PRs, then implementation-ready Issues, and finally untriaged Issues, executing one task per run.

How to run a dev pipeline without human confirmation?▼

Adopt a Human Out of The Loop workflow where the agent never pauses for questions. Instead of adding needs-info labels, it verifies decisions against the codebase, Issue history, and web search, and reports its reasoning when a decision cannot be made.

What labels does this GitHub automation workflow require?▼

It relies on reviewed, in-review, WIP, and needs-info labels to classify PRs and Issues. PRs labeled reviewed without in-review are treated as needing comment resolution, while Issues with reviewed and no WIP are ready for implementation.

Can it close GitHub issues automatically?▼

Yes, it closes Issues already resolved on main, such as when an equivalent fix is merged or the feature was removed. Every close requires a comment citing concrete evidence like commit hashes, PR numbers, or file paths; uncertain cases are left open.

What happens when there are no actionable PRs or issues?▼

If all four priority searches return empty results, the Skill reports that no actionable tasks exist and terminates. It does not create work, ask questions, or wait for new items.

What are the limitations of autonomous dev pipeline execution?▼

It processes only one task per invocation unless asked to continue, and it stops if uncommitted changes block checkout of main rather than stashing or discarding them. All judgments assume an up-to-date main branch pulled at the start.