Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
File-backed workflow harness for reliable Claude Code and Codex sessions.
| Date | Stars |
|---|---|
| 2026-07-31 | 400 |
| 2026-08-04 | 402 |
| 2026-08-06 | 402 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
60.0
growth rate 0.00%/day
<div align="center"> # repo-harness ### A file-backed, repeatable workflow for Claude and Codex coding sessions <img src="docs/images/repo-harness-hook-carrot.png" alt="repo-harness hooks leading Codex and Claude forward with repo-local workflow state" width="900"> [](https://www.npmjs.com/package/repo-harness) [](https://opensource.org/licenses/MIT) [](https://bun.sh) [English](README.md) | [简体中文](README.zh-CN.md) | [日本語](README.ja.md) | [Français](README.fr.md) | [Español](README.es.md) **Give the agent a complete PRD or Sprint; after that, your loop is just review and `next`, or start `/goal` and go AFK.** </div> `repo-harness` ships a CLI plus skill/runtime hooks that write context, plans, handoffs, checks, and review evidence back into the project, so the next agent session continues from files instead of chat memory. It adopts an existing repo with a tasks-first agent contract that keeps Claude and Codex aligned. ## Contents - [Get Started](#get-started) - [Why repo-harness](#why-repo-harness) - [Key Features](#key-features) - [How It Works](#how-it-works) - [Task Workflow](#task-workflow) - [Hooks](#hooks) - [MCP Connector](#mcp-connector) - [Reviewing Work](#reviewing-work) - [Skills](#skills) - [Maintainer Reference](#maintainer-reference) - [Acknowledgements](#acknowledgements) - [Current Release](#current-release) - [License](#license) ## Get Started ### 1. Install the CLI Prerequisites: a Git working tree, `bash`, and `bun`; `jq` is optional. No Node.js required — the installer uses Bun >= 1.1.35 as the runtime, installing or upgrading Bun first when needed. ```bash # macOS / Linux curl -fsSL https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.sh | sh # Windows (PowerShell) irm https://raw.githubusercontent.com/Ancienttwo/repo-harness/main/install.ps1 | iex ``` With Bun >= 1.1.35 already on PATH, skip the shell installer. Package-manager-owned Bun installs fail closed with the matching upgrade command (`brew upgrade bun`) instead of overwriting manager-owned files. ```bash bunx repo-harness@latest install # Bun one-shot bootstrap bun add -g repo-harness # or install the persistent CLI first repo-harness install npx -y repo-harness@latest install # npx fallback; the CLI still runs on Bun ``` ### 2. Bootstrap the host runtime ```bash repo-harness install ``` The global bootstrap: installs the npm package as the global CLI, refreshes repo-harness skill aliases, installs user-level hook adapters, and records an explicit install profile. It is idempotent and does not apply repo-local workflow files to the current directory. `--dry-run --json` lists components to install, skip, and remove first. Profiles, delegation mode, refresh commands, and the read-only `setup check` audit: [`install-profiles.md`](docs/reference-configs/install-profiles.md). ### 3. Preview the repo-local contract ```bash repo-harness init --dry-run ``` Run this from the target repository root. It reports the specs, task state, helper runtime, hook adapter target, and verification files that would be created or refreshed. It never creates an application stack; new projects and modules use `repo-harness-setup`'s scaffold mode instead. ### 4. Apply and verify ```bash repo-harness init bash scripts/check-task-workflow.sh --strict bun test ``` ### Success looks like this Apply ends with `=== Migration Report ===`, naming where generated hook behavior comes from, the user-level `~/.claude/settings.json` and `~/.codex/hooks.json` adapter target, the repo-local surfaces created or refreshed, the `.ai/harness/scripts/*` helper runtime, and an `--- External Tooling ---` readiness block. Stable intent then lives in `docs/spec.md`, execution state in `plans/` and `tasks/`, resume state
Excerpt of 24,897 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:4f704703c3a91c31, llm:Topics: agentic-workflows, ai-agents, claude-code, codex, codegraph, developer-tools, typescript; description: 'File-backed workflow harness for reliable Claude Code and Codex sessions.'
matched fp:4f704703c3a91c31, llm:Topics: agentic-workflows, ai-agents, claude-code, codex, codegraph, developer-tools, typescript; description: 'File-backed workflow harness for reliable Claude Code and Codex sessions.'
matched fp:4f704703c3a91c31, llm:Topics: agentic-workflows, ai-agents, claude-code, codex, codegraph, developer-tools, typescript; description: 'File-backed workflow harness for reliable Claude Code and Codex sessions.'