メニュー
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mountain-loop/yaak --skill release-generate-release-notesコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | release-generate-release-notes |
| description | Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command. |
Generate formatted markdown release notes for a Yaak tag.
git log --oneline <prev_tag>..<target_tag>gh pr view <PR_NUMBER> --json number,title,body,author,urlfeedback.yaak.app)author.login@gschier authors, using by [@handle](https://github.com/handle).by @gschier for PRs authored by @gschier.cli: or only touching crates-cli/) since the CLI has its own release process.After producing notes, ask whether to create a draft GitHub release.
If confirmed and release does not yet exist, run:
gh release create <tag> --draft --prerelease --title "Release <version_without_v>" --notes '<release notes>'
If a draft release for the tag already exists, update it instead:
gh release edit <tag> --title "Release <version_without_v>" --notes-file <path_to_notes>
Use title format Release <version_without_v>, e.g. v2026.2.1-beta.1 -> Release 2026.2.1-beta.1.
Build and run HTTP API requests with the Yaak CLI (`yaak`): create workspaces, folders, environments and variables, author HTTP requests, configure authentication (OAuth 2.0, bearer tokens, API keys, basic, JWT, AWS SigV4), send them individually or a whole folder/workspace at once, chain one request's response into the next, and import existing APIs from OpenAPI, Postman, Insomnia, or cURL. Use this skill whenever the user mentions Yaak, a Yaak workspace, or the `yaak` command, and also when they ask to try, hit, call, exercise, or smoke test an HTTP or REST endpoint, to save or organize API requests for reuse, to set up API requests for manual testing, to add auth to a saved request, to turn an OpenAPI or Postman collection into runnable requests, or to run a saved request suite against staging versus production. Prefer this over one-off `curl` commands whenever the requests should be saved, reused, shared, or run as a set.
Create or edit Yaak changelogs. Beta and draft prerelease changelogs live only in the GitHub release body; stable release changelogs live in `src/content/changelog/YYYYMMDD_VERSION/`. Use when Codex needs to update a beta GitHub release body, generate a stable website changelog from beta releases, update `_release.yaml` or `_intro.md`, expand major entries into markdown files, or preserve Yaak's changelog writing style.