Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
“Draft a new release of the project.”
Install Draft Release
$ npx skills add dyoshikawa/rulesync --skill draft-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dyoshikawa/rulesync draft-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/draft-release .claude/skills/draft-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .claude/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dyoshikawa/rulesync --skill draft-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dyoshikawa/rulesync draft-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.rulesync/skills/draft-release .agents/skills/draft-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .agents/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill draft-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dyoshikawa/rulesync draft-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.rulesync/skills/draft-release .cursor/skills/draft-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .cursor/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dyoshikawa/rulesync.git --path .rulesync/skills/draft-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dyoshikawa/rulesync --skill draft-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dyoshikawa/rulesync draft-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.rulesync/skills/draft-release .gemini/skills/draft-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .gemini/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dyoshikawa/rulesync draft-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dyoshikawa/rulesync --skill draft-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .github/skills && cp -r skills-src/.rulesync/skills/draft-release .github/skills/draft-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .github/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill draft-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dyoshikawa/rulesync draft-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.rulesync/skills/draft-release .opencode/skills/draft-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "draft-release" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release into .opencode/skills/draft-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
draft-release- GitHub stars
- 1.5k
- Token cost
- ~576 tokens
- SKILL.md length
- 313 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
- Works in 2 steps: Confirm that you are currently on the… → Compare code changes between the…
- Calls git, pnpm and gh
About this skill
Draft Release is a skill in dyoshikawa/rulesync (1.5k stars). Its SKILL.md is about 576 tokens. Licence: MIT.
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Confirm that you are currently on the main branch and pull the latest changes. If not on main branch, switch to main branch.
- Compare code changes between the previous version tag and the latest commit to prepare the release description.
What it can do on your machine
Read from SKILL.md and the folder at commit 85bcaf6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpnpmgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, pnpm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Draft Release loads about 576 tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 313 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dyoshikawa/rulesync at commit 85bcaf6, republished under its MIT licence (© dyoshikawa). 313 words, ~576 tokens.
Download SKILL.mdSave it as
.claude/skills/draft-release/SKILL.md (or your agent's skills folder).- name
- draft-release
- description
- Draft a new release of the project.
- targets
- *
First, let's work on the following steps.
- Confirm that you are currently on the main branch and pull the latest changes. If not on main branch, switch to main branch.
- Compare code changes between the previous version tag and the latest commit to prepare the release description.
- Write in English.
- Do not include confidential information.
- Sections,
What's Changed,ContributorsandFull Changelogare needed. ./tmp/release-notes/*.mdwill be used as the release notes.
Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".
If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.
Let's resume the release process.
- Run
git pull. - Run
git checkout -b release/v${new_version}. - Update
getVersion()function to return the ${new_version} insrc/cli/index.ts, and runpnpm cicheck. If the checks fail, fix the code until pass. Then, executegit add,git commitandgit push. - Update the version with
pnpm version ${new_version} --no-git-tag-version. - Since
package.jsonwill be modified, executegit commitandgit push. - As a precaution, verify that
getVersion()insrc/cli/index.tsis updated to the ${new_version}. - Run
gh pr createto the main branch. - Create a draft release using
gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.mdcommand on thegithub.com/dyoshikawa/rulesyncrepository. This creates a draft release so that the publish-assets workflow can upload assets later.
Note: the Homebrew tap formula (Formula/rulesync.rb) is NOT updated here. It embeds sha256 checksums of the release binaries, which only exist after the release PR merges and the Publish Assets workflow uploads them. The goal-release skill performs that update as its post-merge step (regenerate with scripts/generate-homebrew-formula.ts from the release's SHA256SUMS and land it via an immediately merged PR). When releasing manually without the goal-release skill, run that step yourself after the assets are published.
© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .rulesync/skills/draft-release of dyoshikawa/rulesync.
Open the folder on GitHubat commit 85bcaf6
Compare with similar skills
Draft Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Draft Release this skilldyoshikawa/rulesync | 1.5k | — | ~576 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
More from dyoshikawa/rulesync
All 40 skills in this repoRulesync Feature Research
dyoshikawa/rulesync
Maps rulesync feature implementations to upstream coding-agent documentation.
Babysit Dependabot PR
dyoshikawa/rulesync
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…
Commit Push PR
dyoshikawa/rulesync
Commit current changes, push to remote, and create or update a pull request.
Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
Goal PR
dyoshikawa/rulesync
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.
Goal Release
dyoshikawa/rulesync
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…
Related
Works with
Categories
Questions about Draft Release
How do I install Draft Release in Claude Code?
Run `npx skills add dyoshikawa/rulesync --skill draft-release -a claude-code`. Or copy the skill folder (.rulesync/skills/draft-release in dyoshikawa/rulesync) into .claude/skills/draft-release in your project. Claude Code loads it when a task matches its description.
How do I install Draft Release in Codex?
Run `npx skills add dyoshikawa/rulesync --skill draft-release -a codex`. Or copy the skill folder (.rulesync/skills/draft-release in dyoshikawa/rulesync) into .agents/skills/draft-release in your project. Codex loads it when a task matches its description.
Can I use Draft Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill draft-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/draft-release, .gemini/skills/draft-release, .github/skills/draft-release and .opencode/skills/draft-release in your project.
What does Draft Release need to run?
Going by SKILL.md and its folder, Draft Release needs the command-line tools its instructions call (git, pnpm and gh).
Does Draft Release access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Draft Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Draft Release use?
Draft Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Draft Release use?
About 576 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Draft Release?
Skills that share tags, products or a category with Draft Release: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Draft Release?
dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,507 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.
Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.