oh-task

Automate GitHub issue completion from branch worktree to pull request.

3|Updated Jan 7, 2026

Search Tags:#automation #github #issues #workflows #code-review #pull-request

Ready to run

npx skills add https://github.com/open-horizon-labs/bottle --skill oh-task

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oh-task
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/miranda/skills/oh-task
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill oh-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates taking a GitHub issue and driving it to completion in an isolated branch, culminating in a pull request for human review.

Core Features & Use Cases

Autonomous issue handling: claim, branch creation, development work, and PR preparation with minimal user input.
Supports stacked PRs and review follow-ups to ensure dependencies between issues are respected.
Deterministic workflow: fetch origin, create a worktree, run checks, and push a PR with a clear audit trail.
Use Case: A developer uses this in a sprint to auto-branch an issue, implement changes, and open a PR for team review without manual handoffs.

Quick Start

Run the oh-task command with an issue number, for example: /oh-task 42 or /oh-task 42 main to specify the base branch.

Frequently Asked Questions about oh-task

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

FAQPage Schema

How do I automate GitHub issue resolution to create a pull request?▼

Automating GitHub issue resolution involves claiming an issue, creating a branch worktree, implementing changes, and pushing a pull request. This skill drives that entire workflow deterministically up to human review without manual handoffs.

Can I auto-branch and implement code changes from a GitHub issue?▼

Yes, auto-branching from a GitHub issue creates an isolated worktree, reads context, and implements code changes. It runs necessary checks before preparing the branch for pull request publication.

How do stacked pull requests handle issue dependencies in automated workflows?▼

Stacked pull requests manage issue dependencies by enforcing review follow-ups. This ensures dependent changes are respected and reviewed sequentially within the automated GitHub issue workflow.

How do I specify a target base branch when automating a GitHub issue task?▼

Specifying a target base branch when automating a GitHub issue task requires passing the branch name alongside the issue number. The workflow then fetches origin and creates the worktree from that specified branch.

Does automated issue handling work for sprint development without manual handoffs?▼

Automated issue handling works for sprint development by auto-branching issues, implementing changes, and opening PRs for team review. It provides a clear audit trail from issue claim through worktree creation to publication.