jaan-issue-solve

To automate GitHub issue comments, this skill parses a target release changelog to identify referenced closed issues and drafts template-based comments. It ensures safe, idempotent posting by requiring user approval and checking for duplicate comments.

To add release notes without duplicates, use an idempotent commenting process that checks for prior comments before posting. This skill verifies existing comments on closed issues and only posts new template-based release notes after user approval.

Changelog-driven commenting works by reading a GitHub release changelog, extracting issue references, and matching them to closed issues. It then generates tailored template-based comments with version and commit references, posting them only after user approval.

Yes, GitHub CLI authentication is required to post comments on closed issues. After authenticating, you select a target release version, and the skill drafts template-based comments referencing the changelog, posting them only after your approval.

Yes, you can review drafted comments because the skill requires explicit user approval before posting. It generates template-based messages with version and changelog details, then pauses for your review to ensure accurate, context-rich communication.

Using a template for release notes ensures consistent, warm, and context-rich communication across all closed issues. It structures version numbers, commit references, and changelog links automatically, reducing manual effort for maintainers and support teams.