Prepare a sprint delivery review from Linear and GitHub
A delivery review is useful when its scope is explicit. Name the team or project, time window, and repository so the summary does not imply it covers work you did not select.
For product and engineering teams preparing a sprint review or delivery handoff.
What needs to be in place
- In My apps, add Linear and GitHub, then connect accounts with access to the chosen team, project, and repository.
- A bounded sprint or project query, repository name, pull request state, and date window for the review.
In My apps, add the apps listed above and connect the accounts you want your AI client to use. Then connect your AI client to Weavz. A workspace template is optional: it can configure app access and defaults, but your AI client runs the task.
Work through the selected sources
The exact actions available depend on the integrations and actions enabled in the workspace. These steps keep the task bounded to the account and records you selected.
Define the review boundary
Specify the sprint or project, date range, and repository. Do not treat an incomplete list as a full sprint report.
Compare selected records
Search Linear and list pull requests using the specified filters. Match work by issue references and titles, and flag uncertain matches.
Write the review draft
Group verified completions, carryovers, blockers, and decisions. Keep source links and omit unsupported delivery metrics.
App actions and developer details
Action names and inputs
These details help when configuring or implementing the task. You can follow the guide without starting from the action identifiers.
linear.search_issuesSearch issues using the supplied project or sprint query.
Required inputs:
querygithub.list_pull_requestsList pull requests for a specified repository.
Required inputs:
repository
A starting instruction for your AI client
Replace bracketed details with the records and scope you chose. Review the returned result against its sources.
Example instruction
Prepare a delivery review for [Linear team/project or sprint] covering [date range]. Search Linear for [specific project or sprint query] and list GitHub pull requests in [repository] with [state]. Match records only when the reference or context supports the link. Summarize completed work, carryovers, blockers, and open decisions with source links. Do not edit issues, merge code, or post updates.
What the result contains
A scope-labeled delivery review with linked source records and a separate list of uncertain matches.
Keep the source trail with it
Include the search terms, repository, state, and date range in the document title or opening line.
Keep drafts and writes separate
The default result stays in the AI client. Saving the review in Notion or posting it to Slack is a separate write that needs an explicit destination.
If a source or connection is missing
If the Linear query or pull request list is incomplete, revise the scope and rerun the reads. Do not fill missing work from memory or infer unlinked PRs.
Set up the accounts and task
Optional workspace template: Product Ops Hub.
Integrations
Includes Linear, GitHub, and Notion. The template example is a delivery review; the project and date scope still come from you.