post-release-followup

Collect and categorize release findings into actionable follow-up recommendations.

13|6|Updated Apr 14, 2026

Search Tags:#automation #workflow #github #release #issues #triage #follow-up

Ready to run

npx skills add https://github.com/baekenough/second-brain --skill post-release-followup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-release-followup
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/post-release-followup
Command: npx skills add https://github.com/baekenough/second-brain --skill post-release-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After PR creation in the auto-dev release workflow, collect unaddressed findings and present actionable follow-up recommendations. The user can execute now, register as issues, or skip.

Core Features & Use Cases

Collect follow-up candidates from multiple sources: open issues, deep-verify findings, professor-triage outputs, changed-files TODOs, and PR review feedback.
Deduplicate and categorize items into Immediate (execute now), Trackable (register as issue), and Informational (skip).
Present a structured follow-up summary and guide user through choices with a defined action plan and GitHub integration.

Quick Start

Run the post-release-followup skill after a release PR is created to collect findings and generate follow-up actions.

Frequently Asked Questions about post-release-followup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate post-release follow-up actions for open GitHub issues?▼

Collect unaddressed findings by triaging open issues, deep-verify findings, changed-file TODOs, and PR review feedback. The Skill deduplicates these sources and categorizes them into Immediate, Trackable, or Informational follow-ups for structured release workflow management.

What is the best way to triage TODO markers and PR review feedback after a release?▼

Run post-release validation after a release PR is created to collect unaddressed findings and generate follow-up actions. The Skill aggregates workflow outputs, deduplicates items, and presents a structured summary for immediate execution, issue tracking, or skipping.

Can I categorize unaddressed release workflow findings into trackable GitHub issues?▼

Categorize unaddressed findings into Trackable items that can be directly registered as GitHub issues. The Skill integrates with GitHub to map release workflow outputs into structured follow-ups with a user-prompt guided decision flow.

Does post-release follow-up deduplicate findings from multiple validation sources?▼

Post-release follow-up deduplicates findings collected from multiple validation sources, including open issues, deep-verify outputs, professor-triage, changed-file TODOs, and PR review feedback. This ensures a clean, actionable summary without redundant items.

How do I generate a structured follow-up summary from changed-file TODOs and open issues?▼

Generate a structured follow-up summary by analyzing changed-file TODOs and open issues alongside deep-verify and triage outputs. The Skill processes these inputs to produce categorized, actionable recommendations with GitHub issue integration.