OpenParable
Skip to content
← Back to skills

GH Release Notes

Business
gh-release-notes

GH Release Notes is an Agent Skill for business published in the react-cosmos/react-cosmos repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generate a clean list of commits between two git tags for GitHub release notes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/react-cosmos/react-cosmos/blob/HEAD/.agents/skills/gh-release-notes/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-release-notes, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

GitHub Release Notes

Generate a clean commit list between two git tags for GitHub release notes.

Instructions

  1. If a tag argument is provided (e.g. /gh-release-notes v7.2.0), use it. Otherwise, ask the user for the git tag.
  2. Find the previous tag by running git tag --sort=-v:refname and picking the tag immediately after the provided one in the sorted list.
  3. Run git log --pretty=oneline <previous_tag>...<provided_tag> to get the commit list.
  4. Remove any commits containing [release] from the output.
  5. Output the remaining commits as a clean list.
  6. Ask the user for confirmation before creating the release. Show them the exact release name (same as the tag) and the exact body (the clean commit list from step 5). Do NOT proceed without explicit confirmation.
  7. After confirmation, create the GitHub release using gh release create <tag> --title "<tag>" --notes "<commit list>". The release title must be the tag name and the body must be the exact clean list from step 5. Do NOT include a Co-Authored-By line or any tool attribution.