Skip to content

스킬 검색.../

Agent Skill Search Engine

검색

검색
카테고리
직업

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

스킬 파일

Release

Create a new YouMind release — generates release notes, commits, tags, pushes, and creates a GitHub release.

easyspace-ai0 스타2026. 4. 7.

직업
카테고리

Git 워크플로

스킬 내용

Create a YouMind Release

You are creating a release for YouMind version $ARGUMENTS.

Pre-flight checks

Verify the version argument is provided and starts with v (e.g. v0.0.7, v0.0.7-beta)
Verify the working tree is clean (git status)
Verify the tag does not already exist (git tag -l $ARGUMENTS)
Identify the previous release tag (git describe --tags --abbrev=0)

Step 1: Gather release data

Run these in parallel:

git log <prev-tag>..HEAD --oneline — full commit list
git diff <prev-tag>..HEAD --stat | tail -1 — diffstat summary
git log <prev-tag>..HEAD --oneline | wc -l — commit count
Check if docs/releases/<prev-tag>.md exists for style reference

관련 스킬

빠른 설치

Release

npx skillvault add easyspace-ai/easyspace-ai-minote-claude-skills-release-skill-md

Skill 다운로드 저장소 열기

작성자: easyspace-ai
스타: 0
업데이트: 2026. 4. 7.
직업

이 페이지의 내용

01Create a YouMind Release

Step 2: Write release notes

Create docs/releases/<version>.md following the established style:

Start with ## <emoji> <version> — The "..." Release (a punchy, memorable subtitle)
Include release metadata block (date, previous release, range, delta)
Write a 1-2 sentence hook capturing why this release matters
Group changes into 3-6 themed sections with emoji headers:
- AI & Agent — LLM improvements, agent capabilities, tool enhancements
- Knowledge Base — document processing, vector search, memory features
- API & Backend — new endpoints, performance, stability
- UI & UX — frontend improvements, new components, interactions
- DevOps — deployment, configuration, infrastructure
Each section: catchy title, 3-5 bullet points explaining what changed and why it matters
Include an Upgrading section with install instructions
Close with a bold summary line (commit count, lines changed, tagline)

Style guidelines:

Be exciting, energetic, and inspiring — but grounded in what actually shipped
Focus on user-facing impact, not internal refactoring details
Use bold for emphasis on key features
Keep sections scannable with bullet points

Step 3: Show the user the release notes and ask for confirmation

Present the release notes to the user and ask them to review before proceeding. Wait for explicit approval.

Step 4: Commit, tag, push, and create release

After user approval:

Run go vet ./... — fix any issues
git add docs/releases/<version>.md (and any other changed files)
Commit with message: docs: add <version> release notes
git tag -a "<version>" -m "<version>"
git push origin main "<version>"
Create GitHub release:
- For beta/rc versions: gh release create "<version>" --title "<version>" --notes-file docs/releases/<version>.md --prerelease
- For stable versions: gh release create "<version>" --title "<version>" --notes-file docs/releases/<version>.md

Step 5: Verify

Print the release URL
Remind the user that the release is now available
Confirm the docker images can be built with make notex-build

02

Pre-flight checks

03Step 1: Gather release data

04Step 2: Write release notes

05Step 3: Show the user the release notes and ask for confirmation

06Step 4: Commit, tag, push, and create release

07Step 5: Verify

소프트웨어 개발자

Git 워크플로

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Git 워크플로

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Git 워크플로

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Git 워크플로

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Git 워크플로

Repository Setup

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

Significant-Gravitas183.5k

소프트웨어 개발자

Release | Skills Pool