docs
Everything the product does, written down.
Six pages. Two are generated from the code that enforces them; the other four are the maintainers' own notes, rendered from the files they commit.
.pullpulse.yml referenceEvery field, generated from the schema that validates it.→How PullPulse rates a pull requestFour effort tiers and the attention flags, from the file list alone.→What PullPulse posts, and whenPullPulse posts one message per pull request and edits it as things happen. This page covers that message, its thread, and the surfaces around it: the digest, t→Keeping a busy channel quietA channel has one density: how much room PullPulse gives each pull request. Pick it by the volume the channel actually sees, not by preference — a channel that →Releases and what shippedWhen a repository publishes a release, PullPulse posts one card to the channels that asked for it and edits that card as the release deploys.→PullPulse MCP serverPullPulse exposes its review state over the Model Context Protocol so your coding agents can read what the humans see: which pull requests are waiting, why each→