# inrepo

> Bring upstream source into your repo without submodules, forks, or mystery patches.

## Product Summary

- Pin upstream git repositories to exact commits.
- Keep local package changes as reviewable overlay files.
- Rebuild and verify generated checkouts from the same recipe.

## Best Starting Points

- [Overview](/docs/index.md): Why inrepo exists and what files to commit.
- [Quickstart](/docs/quickstart.md): Initialize inrepo, add a package, capture changes, and verify the result.
- [Config](/docs/config.md): Configuration fields, filtering, and generated files.

## When to use Inrepo

Use Inrepo when an agent needs to:

- Vendor upstream Git source directly into a repository at an exact commit.
- Keep local changes as reviewable patch overlays instead of maintaining a fork.
- Rebuild the same generated source tree for teammates or CI.
- Verify that a generated checkout still matches its lockfile and patches.

Do not use Inrepo as a package registry, a replacement for lockfile auditing, or a security boundary.

## How agents should use these docs

Start with the [Quickstart](/docs/quickstart) for the command workflow. Read [Config](/docs/config) before editing an Inrepo recipe. Use the [full documentation context](/llms-full.txt) when the task spans more than one page.