release

Generates bilingual GitHub Release notes from merged pull requests and first-parent commits.

609|50|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/poco-ai/Agentero --skill release-poco-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/poco-ai/Agentero/tree/main/.agents/skills/release
Command: npx skills add https://github.com/poco-ai/Agentero --skill release-poco-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing accurate release notes requires manually reviewing every merged PR and commit between versions, which is error-prone and time-consuming, especially when notes must be published in both Chinese and English. ## Core Features & Use Cases - Evidence Collection: Runs a bundled Node.js script to gather merged pull requests, uncovered first-parent commits, and contributor GitHub usernames for a given release range. - Bilingual Note Drafting: Produces mirrored Chinese and English release notes grouped into Features, Improvements, Fixes, and Resolved Issues, with evidence links and author credits for every bullet. - Draft Release Writing: Writes the notes directly to a Draft GitHub Release via the gh CLI after verifying the tag, workflow status, and assets, with a read-only dry-run mode for review. - Use Case: After the v* release workflow finishes, ask the agent to prepare the release; it resolves the base..target range, collects PR and commit evidence, drafts bilingual notes, and fills the Draft GitHub Release for your approval. ## Quick Start Use the release skill to prepare bilingual release notes for the latest tag and show them for review before updating the Draft GitHub Release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I generate GitHub release notes from merged pull requests?

Run the bundled collect-release-context.mjs script with a base and target ref to gather merged PRs and uncovered first-parent commits as JSON. The skill then drafts grouped bilingual notes with evidence links and writes them to the Draft Release using gh release edit.

How to write bilingual Chinese and English release notes?

Draft the Chinese section first starting at the 概要 heading, then mirror the same groups, bullets, and evidence links in English after a horizontal rule. Keep terminology and factual scope equivalent across both languages rather than shortening one.

Can I preview release notes without changing GitHub?

Yes, request a dry run to get the selected range, PR and commit coverage counts, warnings, and the complete bilingual note candidate. No tag, commit, workflow, or GitHub Release is modified during a dry run.

Does the release skill publish the GitHub Release automatically?

No, it only writes notes to an existing Draft Release after verifying the tag, workflow success, and assets. Publishing with --draft=false, pushing commits, or moving tags requires separate explicit user approval.

Why are some commits missing from the release notes?

Commits covered by a merged PR are attributed to that PR, while uncovered first-parent commits are inspected separately. Release bumps, formatting, tests, and internal refactors are excluded unless they change visible behavior, installation, or security.