Common Template Patterns

[amyryanmanny]

Render

{{- set initiatives = await github.url("https://github.com/orgs/github/projects/12345/views/1") -}}
{{ initiatives.render() |> safe }}

Summarize

{{- set issues = await github.url("https://github.com/orgs/github/projects/12345/views/1") -}}

# [{{ title }} {{ today }}]({{ issues.url }})

{{ issues.remember({ updates: 1, fields: ["Trending"] }) }}
{{ await memory.summarize("tldr") }}

Summarizing a literal list of Issues

{{- set issueNumbers = [
  2,
  3,
  5,
  7,
  11,
] -}}

{{- for issueNumber of issueNumbers -}}
  {{- set issue = await github.issue("github", "repo", issueNumber) -}}
  {{- issue.remember({ updates: 1 }) -}}
{{- /for -}}

{{ await memory.summarize("tldr") }}

Interrogator

This is one of the default templates / prompts. getConfig("key") looks in the Actions inputs / Environment

Template:

{{- set url = getConfig("url") -}}
{{- set query = getConfig("query") -}}

Issues: {{ url }}
Query: {{ query }}

{{ set issues = await github.url(url) }}
{{ issues.remember() }}

{{ await memory.query("interrogate", query) }}

{{ debugMemory() |> safe }}

It injects the context / query in the prompt like so:

name: Interrogate
description: Queries GitHub content
model: openai/gpt-4.1
modelParameters:
  temperature: 0.7
messages:
  - role: system
    content: >
      Query the given GitHub Issues, Comments, and Discussions and provide a concise answer to the given question.
  - role: user
    content: |
      <content>
      {{content}}
      </content>

      <query>
      {{query}}
      </query>

Group by Status

{{ set project = await github.issuesForProjectView("github", 12345, 1) }}

{{ set groups = await project.groupBy("trending") }}
{{ set statuses = ["🔴 high risk", "🟡 at risk"] }}

## {{ project.header }} - Risk Summary

**Overall Status:** {{ project.status("trending") }}

{{ for status of statuses }}

### {{ status |> title }}

{{ set group = groups.find(g => g.groupKey == status) }}
{{ if group === undefined || group.length == 0 }}
Nothing is {{ status |> title }}!
{{ else }}

{{ for issue of group }}
{{ set update = issue.comments.latestUpdate }}
{{ if update }}
- {{ issue.header }} {{ issue.field("trending") }}
  - [Last Update]({{ update.url }}): {{ update.update |> await summarizeToSentence }}
{{ /if }}
{{ /for }}

{{ /if }}

{{ /for }}

Slack DMs

Automatically send DMs to any assignees who have not updated their issue with a comment containing the header "Trending" this week.

{{ set issues = await github.issuesForProjectQuery("github", 12345, query) }}
{{ set blame = issues.blame("lastWeek(Trending),blame()") }}
{{- await blame.dmAssignees("Please add an update, since there has not been one for at least a week. It is needed by a Report.") -}}

The blame arg is optional, and will otherwise default to the value defined under inputs.update_detection

The return type of .blame() is still of the IssueList type, just filtered to the stale issues

Override Update Detection

A common debug use case. Especially useful when testing Update Detection configs locally.

{{- overrideUpdateDetection("TLDR,Ships,Update,skip()") -}}

Summarizing all the comments on a Discussion

{{- set discussion = await github.url("https://github.com/github/repo/discussions/12345") -}}

{{ discussion.remember({ updates: 100 }) }}
{{ await memory.summarize("tldr") }}

Subissues

Recursively include all Subissues in the query like this:

{{ set topIssue = await github.url(..., { subissues: true }) }}

Follow Links (Beta)

This will unpack Issue links inside of the body of the update and treat them similarly to Subissues.

Loop detection was never finished as of 12/29/25, so beware that this might hang when encountering loops. You should make a PR before trying to use this in production.

Discussions similarly are not supported.

{{ set topIssue = await github.url(..., { subissues: true, followLinks: true }) }}
{{ topIssue.remember() }}
{{ await memory.summarize("tldr") }}

{{ debugMemory() |> safe }}