> ## Documentation Index > Fetch the complete documentation index at: https://docs.pullfrog.com/llms.txt > Use this file to discover all available pages before exploring further. # Learnings > Context Pullfrog carries from one run to the next, at the repository, pull request, and organization level. Pullfrog carries context forward between runs, so each run starts with what earlier runs learned about the repository and the PR. | Kind | Scope | Where to edit it | | - | - | - | | Repo-level learnings | Every run in a repository | Repository console, **Agent → Learnings** | | PR-level learnings | Runs on one pull request | Not editable; agent context only | | Cross-repo learnings | [Cross-repo (`--xrepo`)](/flags#cross-repo) runs in an organization | Organization console, **Advanced → Cross-repo learnings** | ## Repo-level learnings Repo-level learnings are durable notes about how a repository works, kept for facts that many future tasks can reuse: * Setup and verification commands, such as the package manager, the lint command, or a targeted test command. * Project conventions, such as where shared utilities live or how components are styled. * Repository gotchas, such as a flaky integration test, a generated file that must not be edited, or a deployment detail that changes how code is validated. * Stable architecture facts, such as which package owns shared runtime logic or where auth decisions are enforced. Pullfrog keeps these notes high-confidence and broadly useful, not a run log. It skips one-off discoveries and guesses, and prunes notes that go stale. You can correct any note in the console, or clear them all. The Learnings card in the repository console ## PR-level learnings PR-level learnings are a rolling summary of one pull request that review and re-review runs read and update: * What the PR changes, and which subsystems, files, or behaviors it affects. * Risks, open questions, and contracts the next review must preserve. * What has been reviewed already, and what changed since the last review. * Earlier feedback that has been addressed or no longer applies. The summary is context for the next run, not a changelog. The review on GitHub carries its own summary for people to read. ## Cross-repo learnings Cross-repo learnings map how an organization's repositories relate, so a [cross-repo](/flags#cross-repo) run does not rediscover the structure each time. Two settings in the organization console, under **Advanced**, hold this knowledge: * **Cross-repo brief** is text you write, and the agent never edits it. State relationships directly: "`api` consumes types from `shared`", "`web` and `mobile` both depend on `design-system`", "run `pnpm -r build` in `platform` before changing downstream repos". * **Cross-repo learnings** are maintained by the agent, like repo-level learnings but for the organization. When the brief leaves the structure unstated, the agent works it out once and records it for later cross-repo runs. The Cross-repo brief and Cross-repo learnings fields in the organization console Keep cross-repo learnings structural: dependency direction, where shared code and types live, and each repository's build and test entry points. Facts about a single repository belong in that repository's own learnings. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.