Skip to main content

❤️ RepoHeart

RepoHeart

The autonomous heart of your GitHub repository.

A 24/7, event-driven, multi-agent system that watches your repo and automatically activates specialized AI agents to triage issues, review PRs, repair CI, resolve conflicts, and keep the repository healthy — safely, and provider-agnostically.


Why

Maintaining an active repository is endless manual work: triaging issues, spotting duplicates, checking what was already fixed, reviewing PRs, watching CI, resolving conflicts, keeping docs current. RepoHeart automates the repetitive parts while keeping humans in control of anything risky.

It runs entirely inside your GitHub Actions workflow — no hosted server, no database, no external infrastructure. Add one workflow, choose an AI provider, done.


How It Works

GitHub Event → Actions runner → normalize + dedup → route to agents
            → each agent retrieves bounded context, reasons, proposes actions
            → Safety Gate authorizes every write
            → results written back to GitHub → run exits (holds no state)

Deterministic where it must be (routing, permissions, idempotency), AI-driven where it helps (the reasoning inside each agent).


Quick Start

1. Add the workflow.github/workflows/repoheart.yml:

name: RepoHeart
on:
  issues:
    types: [opened, edited]
  pull_request:
    types: [opened, synchronize, reopened]
  workflow_run:
    types: [completed]

permissions:
  contents: write
  issues: write
  pull-requests: write

jobs:
  repoheart:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: OpenAgentHQ/repoheart@main
        with:
          config: repoheart.yml

2. Configurerepoheart.yml:

repoheart:
  provider:
    name: opencode          # opencode | claude | openai | gemini | local
    model: your-model
  agents:
    issue_triage: true
    duplicate_detection: true
    pr_review: true
    code_quality: true
    security: true
    ci_repair: true
    conflict_resolution: true

3. Add provider credentials as repository secrets (e.g. OPENCODE_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY).

That's it.


The Agents

Agent Does
Issue Triage Classifies, labels, and summarizes new issues
Duplicate Detection Finds duplicate/related issues
Issue Resolution Detects issues already fixed by prior PRs/commits
PR Review Coherent review of correctness, quality, and risk
Code Quality Lint / format / type checks on changed paths
Security Secret + dependency scanning on the diff
CI Repair Diagnoses CI failures and attempts safe, verified fixes
Conflict Resolution Resolves safe merge conflicts; escalates the rest
Test Test-impact mapping and test generation
Documentation Keeps docs current with changed public symbols

Enable only what you want in repoheart.yml.


Switching AI Providers

Change one line. Agents are untouched.

provider:
  name: claude      # was: opencode
  model: claude-model

Built for Big Repos Too

RepoHeart doesn't load your whole codebase into a prompt. It retrieves only what each event needs — using tree-sitter, ripgrep, and GitHub Search to do the heavy lifting, with event-scoped (sparse/shallow) checkout and an optional content-hash cache. Cost scales with the event's blast radius, not your repo size.


Safety First

Safety first, then correctness, then automation.

  • Every write passes a mandatory Safety Gate.
  • Agents can never escalate their own permissions.
  • No force-push. No auto-merge in the MVP. No committed secrets.
  • Low-confidence or high-risk situations escalate to a human with a clear explanation — never a silent guess, never broken state left behind.

Documentation

Doc Purpose
PROJECT.md Overview and orientation
ARCHITECTURE.md Condensed architecture reference
ROADMAP.md Phased build plan
CONTRIBUTING.md Dev setup and conventions
CLAUDE.md Rules for AI coding agents
docs/repoheart-final-system-design.md Full authoritative system design

Status

v1.0 — Fully Implemented. All 7 roadmap phases complete: deterministic core, provider abstraction, issue intelligence, PR intelligence, large-repo scaling, CI repair & conflict resolution, and documentation agent. 524+ tests passing, ruff clean, mypy strict clean, provider switching config-only. One-workflow + one-config onboarding verified on real repos. See ROADMAP.md for full details.


License

See LICENSE.

RepoHeart is not just a bot. It's an autonomous repository engineering system.

Release files for repoheart 0.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for repoheart 0.8.0
File Size Uploaded
repoheart-0.8.0.tar.gz 246.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for repoheart 0.8.0
File Interpreter ABI Platform
repoheart-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 349.7 kB

Release files / repoheart-0.8.0.tar.gz

Download URL repoheart-0.8.0.tar.gz
Size 246.0 kB
Tags Source
SHA-256 checksum
How to use checksums
a537cc8241058c7ea4b156fb6af35dcaa81a4a1c913797f8f032860053e7f1a6
BLAKE2b-256 checksum
How to use checksums
bd2ae2f9d91446668f61473e03983e415bd4e2284ce75502e985afce337459d1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.

Transparency log

Release files / repoheart-0.8.0-py3-none-any.whl

Download URL repoheart-0.8.0-py3-none-any.whl
Size 103.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4828a4ba8f0a073cbfe4a9bea46dccf29fb62a9cbca2232141e7364c1fab0b21
BLAKE2b-256 checksum
How to use checksums
21ed2a7f76692e19cb33606b325a42752aac33373de3d4aa1d7c9ec0104acffe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.2

2 release files

0.8.1

2 release files

This release

0.8.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page