メニュー
Update the one-liner release description in scripts/release-body.js by analyzing commit titles since the last git tag. Use when the user asks to update the release description, release notes one-liner, or prepare release body for a new version.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Formats GitHub commit messages following Conventional Commits style with title and optional description. Use when proposing or implementing code changes, writing commit messages, or when the user asks for commit message suggestions.
Resolve all merge conflicts on the current branch non-interactively, validate the build, and commit. Use when the user says "fix merge conflicts", "resolve conflicts", or when git status shows conflicting files.
Orchestrates implementation of a multi-task plan by spawning plan-implementer subagents in parallel. Use when the user provides a plan file or plan text and asks to implement it, execute it, or says "implement plan", "run plan", "execute plan".
Resolve on-screen 5chan DOM elements to React source files, line numbers, component names, and ownership stacks using the app's dev-only element-source helpers and playwright-cli. Use when an agent needs to inspect a page element, map a snapshot ref to source code, confirm which component rendered a node, or follow up after $profile-browsing finds a rerender hotspot and needs file-level attribution.
When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. Produces thorough, verified documentation covering local setup, architecture, and distribution.
Test and debug Android APK features using a local Android emulator. Manages emulator lifecycle, builds/installs the APK, runs instrumentation tests, captures logcat diagnostics, and debugs WebView automation (imgur, postimages uploads). Use when the user asks to test APK, debug Android, test uploads, run emulator tests, or says "test-apk".
| name | release-description |
| description | Update the one-liner release description in scripts/release-body.js by analyzing commit titles since the last git tag. Use when the user asks to update the release description, release notes one-liner, or prepare release body for a new version. |
Update oneLinerDescription in scripts/release-body.js before each release.
git tag --sort=-creatordate | head -1
git log --oneline <tag>..HEAD
If there are no commits since the tag, stop — nothing to update.
Categorize by Conventional Commits prefix:
| Prefix | Category |
|---|---|
feat: | New features |
fix: | Bug fixes |
perf: | Performance improvements |
refactor: | Refactors / internal changes |
chore:, docs:, ci: | Maintenance (mention only if significant) |
| No prefix | Read the title to infer category |
Compose a single sentence that summarizes the release at a high level. Rules:
Examples of good one-liners:
Edit oneLinerDescription in scripts/release-body.js (around line 104–105):
const oneLinerDescription = 'Your new one-liner here.';
Read the updated line back to confirm it looks right. The string should: