Engineering
Q
"Why did we switch off express in 2024?"
→
PR #412 migration. Context from ADR-017 and the #eng-decisions thread — performance and middleware debt, per Sarah.
PR #412 · GitHubADR-017 · Notion
Integrations · GitHub
Halyard for GitHub.
Your team's most durable decisions live in PR descriptions and in-repo docs. Halyard indexes them, attributes them, and surfaces them to whatever AI tool your team uses next.
01 · Install
One GitHub App.
Repo-scoped access.
Halyard uses the GitHub App model — you pick which repos to expose. No personal access tokens, no browser extensions, no source-code copies. Revoke at any time from your GitHub org's app settings.
1
Sign in to Halyard and open Integrations.
Find the GitHub tile. You'll need org-admin permissions on the repos you want to index.
2
Install the Halyard GitHub App.
Standard GitHub App flow. Pick "all repositories" or a specific selection. Grants read access to metadata, PRs, issues, and markdown in the selected repos.
3
Halyard indexes in the background.
First pass takes a few minutes. After that, indexing is incremental — PR merges, commits, and issue activity stream in as webhooks.
02 · What Halyard captures from GitHub
Decisions and context, not raw code.
Halyard doesn't pipe your source code into AI. It captures the things that explain the "why" — decisions, rationale, PR conversations, in-repo docs.
→
PR descriptions + review threads
The actual rationale for a change lives in the PR description and the review discussion. Halyard captures both, attributed to authors and reviewers.
→
In-repo docs (ADRs, READMEs, specs)
Markdown files in repos — especially docs/, adr/, specs/ — are indexed as durable knowledge entries with commit-level freshness.
→
Issue + discussion threads
Product-side context lives in issues. Halyard indexes issue bodies, key comments, and linked PR references.
→
Not captured
Source code itself, CI logs, forked content, private gists. Halyard is about decisions, not implementation detail.
03 · What your agents can answer now
The "why" behind the code.
Concrete scenarios where an AI tool grounded in your GitHub history beats one that isn't.
Engineering
Q
"Review this PR for consistency with our auth patterns."
→
Check fastify.config.ts (current pattern), PR #438 (the last auth change), and the #eng-decisions preset.
fastify.config.tsPR #438 · GitHub
Product
Q
"What shipped in the last sprint?"
→
Merged PRs grouped by theme — inline mentions (5 PRs), remediation worker (3), contact model (4).
Closed PRs · Oct week 3Changelog digest
Your PR history, retrievable.
Install the Halyard GitHub App. Your decisions survive the PR merge.