skills.rest
open-horizon-labs
open-horizon-labsOFFICIAL
Explore all skills by this author →
GitHub

oh-notes

Manage GitHub PR feedback by creating isolated worktrees and guiding fixes.

3|Updated Jan 7, 2026
Search Tags:#automation#GitHub#worktree#PR#code-review#oh-notes
One-click install
npx skills add https://github.com/open-horizon-labs/bottle --skill oh-notes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oh-notes
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/miranda/skills/oh-notes
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill oh-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Address PR comments on GitHub issues and help teams push fixes efficiently by coordinating isolated worktrees and automated review steps.

Core Features & Use Cases

  • Automated PR feedback handling: Read and organize feedback from PRs, create worktrees per task, and prepare fixes.
  • Descendant issue workflow: Spawn GitHub issues for non-trivial feedback to track tasks and resolutions.
  • Use Case: A maintainer runs /oh-notes 42 to address PR #42, fixes code, and pushes a clean patch.

Quick Start

Use the oh-notes command to address a PR: /oh-notes <pr-number>.

Frequently Asked Questions about oh-notes

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

FAQPage Schema
How do I automate addressing GitHub PR feedback and pushing fixes?▼

You can automate addressing PR feedback by running the oh-notes command with a PR number to read comments, create an isolated Git worktree, and guide code fixes before pushing patches. It coordinates review resolutions by navigating PRs and preparing fixes directly.

What is the best way to manage isolated worktrees for GitHub PR code reviews?▼

Managing isolated worktrees for PR reviews involves generating a worktree per task based on PR comments to isolate fixes and coordinate branches. This workflow optionally spawns descendant GitHub issues to track non-trivial feedback and resolutions across your repository.

Do I need the gh CLI to resolve GitHub PR comments with an automated workflow?▼

Yes, you need the gh CLI along with Git and specific oh-notes workflow conventions to resolve PR comments automatically. These dependencies are required to navigate pull requests, create worktrees, initialize superego, and optionally spawn descendant issues for larger fixes.

Can I track non-trivial PR review feedback as separate GitHub issues?▼

Yes, you can track non-trivial PR review feedback as separate GitHub issues using a descendant issue workflow. When addressing PR comments, the system optionally spawns descendant issues to coordinate tasks and track resolutions for larger fixes across branches.

Why create an isolated worktree for each PR review fix?▼

Creating an isolated worktree for each PR review fix prevents branch conflicts and keeps code changes organized per task. It allows you to address specific PR comments, apply fixes, and push clean patches without disrupting the main branch or other ongoing review resolutions.

Related Skills

Explore More Software Engineering Skills→
lenadlmlenadlm

github-code-review

Automate GitHub code review workflows with git commands and inline comments.

Community
Advanced
timogilvietimogilvie

git-workflow-manager

Automate Git branch creation, structured commits, and pull requests.

Community
Intermediate
bacchus-labsbacchus-labs

docs-audit-fix

Coordinate automated documentation fixes across Git worktrees and pull requests.

Official
Advanced
mlflowmlflow
1

add-review-comment

Post review comments to GitHub pull requests via the GitHub CLI.

Official
Intermediate