repo-native-alignment: Skill for Claude Code

.agents/skills/oh-notes/SKILL.md

oh-notes is a skill for Claude Code, Codex from open-horizon-labs/repo-native-alignment. It costs 19 tokens per session (2,102 once invoked), scanned A, original, MIT.

A workflow for handling comments on GitHub pull requests, which are proposed code changes awaiting review. It uses a separate Git worktree, applies fixes, and pushes the updated branch.

In plain words
What is it for?
Use it to address review comments on pull requests created by the related oh-task workflow, resolve requested changes, and push the fixes.
Why use it?
It gathers review feedback and connects the changes to the related GitHub issue, reducing the chance of editing the wrong branch or missing comments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is open-horizon-labs/repo-native-alignment's own configuration. It tells Claude Code and Codex how to work on repo-native-alignment itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repo-native-alignment configures →

Reuse

Borrowing it

Nothing to install: this file belongs to open-horizon-labs/repo-native-alignment. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/open-horizon-labs/repo-native-alignment/main/.agents/skills/oh-notes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignment

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for oh-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-notes/github.svg)](https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-notes)
Your own site
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-notes"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-notes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for oh-notes

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-notes"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.02102
Opus 5 $0.00010 $0.01051
Sonnet 5 $0.00004 $0.00420
Haiku 4.5 $0.00002 $0.00210

Measured 10d ago against content hash cf6220da4739, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

oh-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/oh-notes/SKILL.md · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.

oh-notes

Address feedback on a PR created by oh-task: work in an isolated worktree, resolve comments, push fixes, and use linked GitHub issues for descendant work.

Invocation

/oh-notes <pr-number>

  • <pr-number> - the pull request number to address comments on

Prerequisites

  • Repo context: Run from the repo root where the PR exists
  • GitHub issue PR: The PR should be from an oh-task session (branch issue/<number>)

Flow

  1. Load project background from AGENTS.md, relevant .oh/ artifacts, and RNA MCP context when available.

  2. Get PR branch info and create worktree:

    # Save original directory for cleanup
    ORIGINAL_DIR=$(pwd)
    
    # Get the PR branch name and linked issue
    BRANCH=$(gh pr view <pr-number> --json headRefName -q .headRefName)
    
    # Extract issue number from branch (issue/<number>)
    PARENT_ISSUE=${BRANCH#issue/}
    
    # Fetch and create worktree tracking the remote branch
    git fetch origin
    git worktree add .worktrees/pr-<pr-number> -B $BRANCH origin/$BRANCH
    cd .worktrees/pr-<pr-number>
    

    Note: -B $BRANCH creates/resets the local branch to track origin.

  3. Fetch PR comments (both top-level and inline review comments):

    gh pr view <pr-number> --json comments,reviews
    gh api repos/{owner}/{repo}/pulls/<pr-number>/comments --paginate --slurp
    
  4. Identify unresolved comments:

    • Focus on actionable feedback requiring code changes
    • Ignore resolved/outdated comments
    • Skip non-actionable noise (e.g., "Thanks for the PR!")
  5. For each unresolved comment: a. Understand the feedback b. Make the fix c. Stage changes (git add) d. Run the repo-local /review skill on staged changes e. Handle review findings:

    • P1-P3 trivial (one-liner fix): fix inline, re-stage, re-review
    • P1-P3 non-trivial (significant change): create GitHub issue as descendant
    • P4: discard (nitpick)

    Creating descendant issues:

    # Create issue linked to parent
    NEW_ISSUE=$(gh issue create \
      --title "Fix: <brief description>" \
      --body "Spawned from #${PARENT_ISSUE} during PR #<pr-number> review.
    
    ## Context
    <what repo-local review found>
    
    ## Acceptance
    - [ ] Fix applied
    - [ ] repo-local review passes" \
      --assignee @me | grep -oE '[0-9]+$')
    
    echo "Created descendant issue #${NEW_ISSUE}"
    

Read the full file on GitHub · 291 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 291 lines · 19 tokens per session scan A cf6220da4739

Subscribe to this mod's changes

oh-notes is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 2,102 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…

daymade/claude-code-skills · 133 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

write-pr

Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.

tldraw/tldraw · 53 tokens