harness-contextlisted
Install: claude install-skill mifunedev/openharness
# Harness Context
Use this skill when the user asks about Open Harness layout, lifecycle,
conventions, git workflow, or where files live.
## Steps
1. Read `CLAUDE.md` for the orchestrator contract — what the root-level
agent does and does not do.
2. For layout questions, read the per-directory `README.md` files (e.g.
`.oh/README.md`, `.oh/crons/README.md`, `.oh/tasks/README.md`,
`.oh/scripts/README.md`, `.oh/worktrees/README.md`) and the `Project
Structure` section of `CLAUDE.md`. There is no single comprehensive
tree — use the filesystem and the directory READMEs.
3. For behavioral norms (formerly the `.oh/context/rules/` tier, collapsed into
on-demand skills in B-state M4), the canonical homes are now:
- `/git` (`.oh/skills/git/SKILL.md`) — issue / branch / commit / PR conventions
- `/t3` (`.oh/skills/t3/references/sandbox-processes.md`) — tmux sessions for long-running processes
- `.oh/context/directory-readme.md` — when a directory needs a README
- the `advisor` agent (`.oh/agents/advisor.md`) — pattern for delegating to sub-agents
4. For skill-listing or skill-source-of-truth questions, load `references/skill-source-of-truth.md` and separate the tracked Open Harness shared skill library (`.oh/skills/*/SKILL.md`, exposed through `.claude/skills`, `.codex/skills`, `.pi/skills`, and Hermes' runtime `.hermes/skills/openharness` symlink) from the active Hermes runtime catalog (`.hermes/skills/` plus bundled/profile skills). Do not present `her