post-release-followup

Analyze release artifacts and repository metadata to categorize follow-up tasks.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill post-release-followup-hiddink-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-release-followup
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/post-release-followup
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill post-release-followup-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the post-release gap where unaddressed findings, TODO markers, and PR feedback often remain scattered and ignored, preventing systematic project improvement.

Core Features & Use Cases

  • Unified Findings Collection: Aggregates deferred issues, deep-verify outputs, TODO markers, and PR review feedback into a single actionable list.
  • Intelligent Categorization: Automatically sorts findings into immediate execution, issue registration, or informational reference based on severity.
  • Workflow Integration: Streamlines the transition from release completion to maintenance by delegating tasks to specialist agents or creating GitHub issues via the CLI.

Quick Start

Execute the post-release-followup skill to collect and triage all pending release findings and PR feedback for the current session.

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 triage for deferred issues and code markers?

Automate post-release triage by analyzing release workflow artifacts and repository metadata to categorize deferred issues, TODO markers, and PR review feedback into an actionable tracking list.

How does PR review feedback integration work for GitHub release workflows?

PR review feedback integration works by aggregating review comments with deep-verify outputs and deferred issues, sorting them by severity for immediate execution or GitHub issue registration via the CLI.

Do I need GitHub CLI integration to track post-release follow-up tasks?

Yes, you need GitHub CLI integration and file system access to process session outputs, manage repository metadata, and generate tracking issues for post-release follow-up tasks.

What is the best way to consolidate unaddressed TODO markers and PR feedback after a release?

The best way to consolidate unaddressed TODO markers and PR feedback is to execute a unified findings collection that automatically categorizes them by severity for immediate execution or informational reference.

Can I use this workflow to automatically create GitHub issues for unaddressed findings?

Yes, you can use this workflow to automatically create GitHub issues via the CLI, streamlining the transition from release completion to maintenance by registering unaddressed findings that require tracking.

When should I not use automated triage for post-release follow-up tasks?

Automated triage for post-release follow-up tasks should not be used when your project lacks GitHub CLI integration or file system access, as these are required to analyze artifacts and generate tracking issues.