repo-native-alignment: Skill for Claude Code

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

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

A workflow for resolving merge conflicts on a GitHub pull request by bringing the latest base branch into the proposed changes. A merge conflict occurs when Git cannot safely combine different edits to the same code.

In plain words
What is it for?
Use it when GitHub reports that a pull request cannot be merged cleanly. It helps fetch the branches, merge the base into the pull request, resolve conflicts, verify the result, and push the update.
Why use it?
It provides an isolated workspace and requires understanding the pull request's linked issue before resolving conflicting changes. This helps preserve the purpose of both the new work and the base branch.

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-conflict/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-conflict

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-conflict/github.svg)](https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-conflict)
Your own site
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-conflict"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-conflict/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-conflict

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-conflict"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-conflict.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,549 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.00015 $0.01549
Opus 5 $0.00008 $0.00775
Sonnet 5 $0.00003 $0.00310
Haiku 4.5 $0.00002 $0.00155

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

Security

Grade A, and why

oh-conflict 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 11d 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-conflict/SKILL.md · 200 lines

How it starts

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

oh-conflict

Resolve merge conflicts on a pull request. Work in an isolated worktree, merge the base branch into the PR head, resolve conflicts with understanding of both sides' intent, verify, and push.

Invocation

/oh-conflict <pr-number>

  • <pr-number> - the pull request number with merge conflicts

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:

    # Save original directory for cleanup
    ORIGINAL_DIR=$(pwd)
    
    # Get head and base branch names
    PR_INFO=$(gh pr view <pr-number> --json headRefName,baseRefName)
    BRANCH=$(echo "$PR_INFO" | jq -r .headRefName)
    BASE=$(echo "$PR_INFO" | jq -r .baseRefName)
    
  3. Create worktree and set up:

    git fetch origin
    git worktree add .worktrees/conflict-<pr-number> -B $BRANCH origin/$BRANCH
    cd .worktrees/conflict-<pr-number>
    
  4. Understand the PR's intent before merging:

    # Read the linked issue to understand what this PR is trying to do
    PARENT_ISSUE=${BRANCH#issue/}
    gh issue view $PARENT_ISSUE
    
    # See the PR's own changes (what this branch introduced)
    git log --oneline origin/$BASE..$BRANCH
    git diff origin/$BASE...$BRANCH --stat
    
  5. Attempt the merge:

    git merge origin/$BASE --no-edit
    

    This will fail with conflict markers in affected files.

  6. Resolve conflicts file by file:

    • For each conflicted file, read both sides:

      git diff --name-only --diff-filter=U  # List conflicted files
      
    • Understand the intent of BOTH sides:

      • Ours (HEAD/PR branch): What did this PR change and why?
      • Theirs (base branch): What changed on base since this PR branched?
    • Resolve by preserving the intent of both sides

    • If the PR's changes are superseded by base, accept theirs

    • If both sides changed the same logic, merge the intents

    • Stage each resolved file: git add <file>

Read the full file on GitHub · 200 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. 11d ago First seen · 200 lines · 15 tokens per session scan A 989b3f2f323b

Subscribe to this mod's changes

oh-conflict is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 1,549 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

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens