Publish a changelog of what shipped this week

Publish a changelog of what shipped this week

Drafts a changelog of the week's GitHub and Linear work in Notra, shows it to you for edits, and publishes it once you approve.

Set up the tools below, then run the steps in order for the user, carrying each step's results into the next. The run is done when the user has the outcome below.

Outcome

• A changelog of the week's work, drafted by Notra in your brand's voice.
• The changelog published in Notra after you approve it, with any edits you asked for.

Inputs

Ask the user for this before you start.

• lookback: the stretch of work to cover, one of Notra's lookback windows, e.g. last_7_days

Set up

Notra (tool:notra/generate-post, tool:notra/update-post)

Use the first option your agent supports.

Notes:

• Generate a post: Returns a jobId; poll get_post_generation_status (GET /v1/posts/generate/{jobId}) until the draft is ready. lookback picks the activity window, from current_day to last_30_days.
• Update or publish a post: Sending markdown re-renders the stored HTML. Slugs are accepted only for blog posts and changelogs.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "notra": { "url": "https://mcp.usenotra.com/mcp" } } }

• Generate a post: call the MCP tool generate_post
• Update or publish a post: call the MCP tool update_post

CLI (official)

Install the command and sign in with it, then confirm it runs.

npm i -g notra
notra --version

• Generate a post: run notra posts generate
• Update or publish a post: run notra posts update

Before step 1, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Steps

1. Draft the changelog with Generate a post (Notra). Queue a post with contentType set to changelog and lookbackWindow set to lookback, then poll the job until it is completed, failed or skipped. Keep its postId; if the job did not complete, tell the user why and stop.
2. Review the draft yourself. Read the post Notra made and show its title and markdown to the user. Make the edits they ask for, and keep the final title and markdown.
3. Publish with Update or publish a post (Notra). After the user approves, update the post with the final title and markdown, and set status to published.

Notes

Notra drafts from the GitHub and Linear integrations connected to your organization. Run it once a week, after your last release.

Rules

• Use only the services set up above. The read-only calls they need, like listing ids or polling for results, are fine.
• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.