vncp

Rematch — Development skill for Claude Code

Development community

Harness improvement from real sessions for omp, Claude Code and Codex: traces every session, proposes skills, scripts, hooks and subagents grounded in execution traces, stages them provisional, keeps.

How to install Rematch

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vncp/rematch and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Rematch does

Harness improvement from real sessions for omp, Claude Code and Codex: traces every session, proposes skills, scripts, hooks and subagents grounded in execution traces, stages them provisional, keeps only what later sessions confirm. One shared skills library, bitemporal history lake, git-synced profile.

Alternatives in Development

  • Claude Hooks Mastery — 3,300+ Complete mastery guide for Claude Code hooks with production-ready scripts 3.4k ★
  • Arreflect — AgentRecall consolidation & reflection — periodic triage of recurring corrections; proposes rule changes, neve 370 ★
  • Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★

README

rematch

Stop teaching your coding agent the same lesson every session.

rematch turns corrections from your sessions into reusable skills and guardrails, then tracks whether the same problems recur in later, matching sessions. It changes the agent's instructions and tools—not model weights—and does not guarantee improvement.

Start · Harnesses · Commands · Docs

Quick start

You need a Rust toolchain and **omp with working model access**. omp is the runtime for rematch's editor and classifier calls, even when you work in Claude Code or reflect on Codex history. The omp extension targets omp 18.12.

From a checkout of this repository:

scripts/install.sh
export PATH="$HOME/.local/bin:$PATH"
rematch doctor --text

The installer builds the binary, links the omp extension and puts a `rematch` shim in `~/.local/bin`. Keep the checkout: the shim points to its release binary. Then start omp and work normally. A correction can flag a session for reflection in the background at the next session start; a proposal is not guaranteed.

Optionally seed the ledger from existing omp sessions:

rematch import --history --harness omp

Model roles come from your omp configuration: `rematch-editor` falls back to `slow` → `default`; `rematch-classifier` to `smol` → `tiny` → `default`. See [installation](https://vncp.github.io/rematch/start/install/) and [model roles](https://vncp.github.io/rematch/reference/configuration/model-roles/) for setup details.

Harness support

All three use the same binary, library and counters. Their integration is not ident