You need a GitHub connection with read access to the target repository and a Notion connection with edit access to your destination page.
Fetches pull requests, their descriptions, and available change details from the repository you authorize.
Specify a repository and date range. Leina drafts a source-linked summary of pull requests in chat, then appends the update to your Notion page on your cue.
Engineering weekly update
acme/workspace · Oct 5–9 · Draft for Notion
Ready for review in team chat
Next request: “Add the reviewed update to our Notion page.”
Ask for the draft in chat, review the source references, and send a follow-up request to save the update in Notion.
Connect the tools you want Leina to read from and update.
Fetches pull requests, their descriptions, and available change details from the repository you authorize.
Appends the structured summary under your chosen heading on your Notion page.
Draft and review the update in team chat, then ask Leina to save it to Notion.Set Up Leina in Slack
Specify the repository, date boundaries, and timezone. Ask for pull requests merged during that period, along with any currently open work.
Leina generates a structured summary with links to each pull request. Spot-check the merged list against your repository and review any flagged gaps.
Send a follow-up prompt with your Notion page URL. Leina writes the section under your designated heading and returns the page link.
Replace the bracketed values with your own, then send the prompt in your connected chat.
@Leina Prepare a weekly update for [owner/repository], from [start timestamp] through [end timestamp] in [timezone]. List PRs merged in that window with their titles, links, and brief summaries based on available descriptions and changes. Group currently open PRs in a separate section with their current status. State the retrieval timestamp. Flag any undocumented changes or incomplete retrieval. Return the draft here first; do not write to Notion yet.
@Leina Append the reviewed update to [Notion page URL] under [repository — reporting period]. Check whether that heading already exists before writing, preserve all other page content, read back the saved section, and return the page link. If the write outcome is uncertain, inspect the page before retrying.
Start with a completed week to easily spot-check results against GitHub. Verify that the merged PR list matches your repository search, and note that merged pull requests reflect merged code rather than production deployments. Open PRs reflect current repository status at the time of your query.
Read the full guide for configuring date boundaries, handling missing descriptions, and structuring Notion updates.
Use this Markdown template as a clean starting format for your team's weekly engineering reports.
You need a GitHub connection with read access to the target repository and a Notion connection with edit access to your destination page.
The example prompts ask for a draft in chat first, followed by a separate request to append it to Notion. This review step is part of the workflow you request; connection permissions and action settings still apply.
Yes. Keep the prompt structure and update the date boundaries each week. You can also save the prompt to run on a recurring schedule once you are happy with the format.
Connect the accounts you need, request a scoped task, and review the result.
Connect Your AppsKeep improving your export website with Leina: uncover search opportunities, improve product pages, write blog posts, and use performance data to plan the next update.
View SolutionKeep buyer inquiries moving with Leina: review Gmail and Outlook threads, check CRM context, draft replies, and plan the next follow-up.
View SolutionKeep inventory and shipments in view with Leina: use Lingxing, Shopify, AfterShip, and HaiGuanJia records to reconcile stock, identify risks, and prepare replenishment and exception follow-ups.
View SolutionQuery product event metrics and get daily breakdown tables alongside visual charts in your Slack thread.
View Solution