ysskrishna logoysskrishna

Chapter 9 of 9 ยท 2 min

Putting it together: a release-notes workflow

Build one small workflow that uses a skill, a subagent, an MCP server and a hook, then review it with a checklist.

You now have all four parts. This chapter combines them into a workflow you can adapt: "Write this week's release notes and prepare them for Slack." Each part does one job, and you can remove any part and still understand what is left.

The design

PartFileJob
Skill.claude/skills/release-notes/SKILL.mdHouse format and rules
Subagent.claude/agents/changelog-scout.mdRead merged PRs on a small model, return a compact list
MCP serverMarkdown Convert MCPConvert the Markdown draft to Slack mrkdwn
Hook.claude/settings.json (PreToolUse)Block any Slack send tool unless .release-approved exists

Step 1: the skill

---
name: release-notes
description: Write weekly release notes from merged PRs in our house format. Use when the user asks for release notes, a changelog or "what shipped". Skip for single-PR descriptions.
---

# Release notes

1. Delegate PR collection to the `changelog-scout` agent with the date range.
2. Group into Features, Fixes, Internal. Drop dependency bumps.
3. One line per item: user-facing change, then (#PR).
4. Open with one sentence naming the most important change.
5. Produce Markdown. If the user wants Slack, convert with `markdown_to_slack` before handing it to the Slack tool. Do not send; show the draft and wait.

Step 2: the subagent

---
name: changelog-scout
description: Collect merged PRs for a date range and return title, number and one-line user-facing summary for each. Read-only.
tools: Bash, Read
model: haiku
---

Run `gh pr list --state merged --search "merged:>=<START>" --json number,title,body --limit 100`.
Return one line per PR: `#<number> | <title> | <one-line summary>`. No commentary. Max 60 lines.

The scout reads up to 100 PR bodies; the main chat receives at most 60 short lines.

Step 3: the MCP server

Connect Markdown Convert MCP (chapter 7). The skill tells the agent when to use markdown_to_slack: only for an API send, never before a paste into Slack's composer.

Step 4: the hook

#!/usr/bin/env bash
# .claude/hooks/require-approval.sh  (PreToolUse, matcher: slack tools)
if [ ! -f .release-approved ]; then
  echo "Sending is blocked until a human creates .release-approved. Show the draft instead." >&2
  exit 2
fi

Register it with a matcher for your Slack tool's name (MCP tools appear as mcp__<server>__<tool> in Claude Code).

Step 5: run it

  1. New session. Ask: "Release notes for everything merged since Monday, for Slack."
  2. Watch for: the skill's structure, a changelog-scout task, a markdown_to_slack call, and the hook blocking the send.
  3. Review the draft. When happy, touch .release-approved and ask the agent to send. Delete the file afterwards.

Review checklist

Use this on any workflow you build:

  • One job per part. No skill that tries to enforce, no hook that tries to teach.
  • Descriptions match real requests. You tested the trigger phrases.
  • Output contracts. Every subagent returns a bounded, structured result.
  • Least privilege. Subagent tools and MCP servers limited to what the job needs.
  • A human gate before anything external. Sends, deploys and deletes need an explicit approval, enforced by a hook.
  • Receipts. You can tell which model ran and which tools were called.

Where to go next

Quick check

  1. Which part keeps 100 PR bodies out of the main conversation?The changelog-scout subagent.

  2. What guarantees the notes are not posted before review?The PreToolUse hook that blocks the send tool until .release-approved exists.

  3. You remove the skill. What breaks?Format consistency and the "when to convert" judgment. The scout, converter and hook still work, but the agent improvises the notes.

Continue exploring

Productnpm+3Thinking Methods

Thinking Methods

17 well-known thinking methods your AI coding assistant can actually run.
Agent Skills
AI Apps & Assistants
Bash
Gemini
BlogCover image for 17 Thinking Skills for AI Agents: Pre-Mortem, Five Whys, Six Hats and More

17 Thinking Skills for AI Agents: Pre-Mortem, Five Whys, Six Hats and More

AI Apps & Assistants
Agent Skills
4 min read
ToolCover image for AI Token Counter

AI Token Counter

AI token counter with model pricing and context-window comparison in your browser.

Chat & AI
AI Apps & Assistants
+1
Productskills.sh+1Claude Code Subagents for Cursor

Claude Code Subagents for Cursor

Your Cursor subagents can finally run on the model you picked in each agent file.
Chat & AI
Agent Skills
AI Apps & Assistants
Bash
CourseCover image for Prompt Engineering for Coding Agents

Prompt Engineering for Coding Agents

Write prompts that coding agents act on: clear goals, the right context, output contracts, examples, structured thinking, shorter answers and a tiny eval set.

Agent Skills
Chat & AI

8 chapters ยท 21 min

BlogCover image for How to Install Caveman in Cursor and Claude Code

How to Install Caveman in Cursor and Claude Code

AI Apps & Assistants
Agent Skills
+1
3 min read