Pull Request Linking

Pull Request (PR) linking associates architectural decisions and codebase patterns with the actual implementation work in your version control platform.

Managing PR Links

You can manage PR links using the dedicated pr command, or attach them inline when logging new decisions.

1. Adding PR Links

To attach one or more PR links to an existing decision or pattern: 

engrams pr add --type decision --id 4 --pr 42 --pr 43
engrams pr add --type pattern --id 1 --pr "https://github.com/org/repo/pull/101"

Alternatively, you can attach PRs immediately when creating a decision: 

engrams decision log --summary "Use AES-GCM-256 encryption" --pr 42

Automatic PR URL Resolution

Engrams makes linking fast by automatically converting raw PR numbers into full URLs. If you provide a numeric PR (e.g. 42), Engrams inspects your Git remote configuration (e.g. origin) to resolve the GitHub repository URL automatically, producing: https://github.com/stevebrownlee/engrams-cli/pull/42.

2. Listing PR Links

To view all PR links currently attached to an item: 

engrams pr list --type decision --id 4

The command returns a JSON array of registered PR links: 

[
  {
    "url": "https://github.com/stevebrownlee/engrams-cli/pull/42",
    "timestamp": "2026-07-12T10:15:30Z"
  }
]

3. Removing PR Links

To remove a specific PR link from an item: 

engrams pr remove --type decision --id 4 --url "https://github.com/stevebrownlee/engrams-cli/pull/42"

Traceability and Audit Health

Linking your decisions directly to PRs keeps your knowledge base complete and transparent:

  • Traceability: Developers and AI agents can jump straight from an architectural decision in the CLI to the code diff and discussion thread where it was implemented.
  • Completeness Auditing: Running the doctor command automatically flags active decisions that lack associated PR links, helping maintain compliance and documentation standards.