SkillsAdd

open-horizon-labs/repo-native-alignment · Archived

oh-task

Claim a GitHub issue, create its branch and draft PR before implementation, execute the work in isolation, and hand the completed draft to RNA's full ship gate.

First seen Aug 6, 2026

Installation

$ npx skills add open-horizon-labs/repo-native-alignment --skill oh-task
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

record Same source · more installs
open-horizon-labs/repo-native-alignment

Create or update repo-native outcomes, objectives, capabilities, signals, guardrails, metis, an…

10 installs
setup Same source · more installs
open-horizon-labs/repo-native-alignment

Install and configure the Repo-Native Alignment (RNA) MCP server. Downloads the binary, configu…

9 installs
dead-code Same source · more installs
open-horizon-labs/repo-native-alignment

Detect potentially dead code using RNA graph data. Finds public functions with zero non-test ca…

7 installs
review-readiness Same source · more installs
open-horizon-labs/repo-native-alignment

Agent-led PR/working-tree review triage. Start from the diff, add RNA graph/business context on…

7 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

gws-tasks Similar name
googleworkspace/cli

Google Tasks: Manage task lists and tasks.

39.5K installs
gws-workflow-email-to-task Similar name
googleworkspace/cli

Google Workflow: Convert a Gmail message into a Google Tasks entry.

29.4K installs
recipe-create-task-list Similar name
googleworkspace/cli

Set up a new Google Tasks list with initial tasks.

27.3K installs
recipe-review-overdue-tasks Similar name
googleworkspace/cli

Find Google Tasks that are past due and need attention.

27.2K installs
task-management Similar name
anthropics/knowledge-work-plugins

Simple task management using a shared TASKS.md file. Reference this when the user asks about th…

6.8K installs
trigger-tasks Similar name
triggerdotdev/skills

Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(…

2.7K installs

Also in this package

Other skills from open-horizon-labs/repo-native-alignment · top by installs.

npx skills add open-horizon-labs/repo-native-alignment
record 10 setup 9 dead-code 7 review-readiness 7 adr-sync 6 arch-diagram 6 oh-review 1 execute 1 ship 1 teach-oh 1

Browse all from open-horizon-labs/repo-native-alignment

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch main
Open issues 26
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,894 B
  • docs SUMMARY.md 175 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

oh-task

Work a GitHub issue through the repository's mandatory draft-PR-first workflow.

Invocation

/oh-task <issue-number> [base-branch]

The base defaults to main. Use another branch only for an intentional stacked PR.

Flow

  1. Load AGENTS.md, relevant .oh/ artifacts, and RNA context.
  2. Fetch and validate the open issue. Stop if it is closed, owned by someone else, or lacks enough information to proceed.
  3. Claim the issue with gh issue edit <issue> --add-assignee @me.
  4. Run the repo-local /aim, /problem-space, /problem-statement, and /solution-space phases at the altitude required by the issue. Record the chosen solution.
  5. Create an isolated branch/worktree from the selected base.
  6. Before changing implementation files, push the branch and open a draft PR:

```bash git push -u origin issue/<number> gh pr create --draft --base <base-branch> --title "<issue-title>" --body "Closes #<number>

## Problem <problem statement>

## Chosen solution <solution-space recommendation>" ```

  1. Execute the chosen solution. Keep all work within the declared issue scope.
  2. Run project checks and the repo-local /review skill. Fix every actionable finding.
  3. Commit focused changes tagged with the relevant [outcome:X] and push them to the draft PR.
  4. Complete any descendant issues created during execution before declaring the implementation complete.
  5. Invoke repo-local /ship <PR-number>. That pipeline alone marks the PR ready, handles CI, verifies delivery, obtains explicit approval of the final diff from a fresh, separate repo-local /review sub-agent, and merges.
  6. Clean up the worktree only after /ship completes or reports a blocker.

Guardrails

  • Never implement before the draft PR exists.
  • Never mark the PR ready or merge directly from this skill.
  • Never substitute a lightweight review for the full RNA /ship pipeline.
  • Never merge without an explicit APPROVE from a fresh, separate repo-local /review sub-agent on the current final diff. Any later diff change invalidates approval and requires a new fresh reviewer.
  • Never trigger or wait for CodeRabbit. If actionable CodeRabbit comments already exist, address them like any other external review feedback.
  • Use AGENTS.md, .oh/, and RNA for context; do not depend on external task-memory tools.
  • If completion signaling is unavailable, report COMPLETION: status=<status> pr=<url>.

Exit conditions

  • Success: /ship merged the PR and verified delivery.
  • Blocked: a human decision or mandatory ship gate prevents progress.
  • Error: the issue, branch, PR, or verification workflow cannot be completed safely.