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.
Run the complete Effect Machine implementation and release workflow in this repository.
Install Effect Machine Release
$ npx skills add typeonce-dev/effect-machine --skill effect-machine-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install typeonce-dev/effect-machine effect-machine-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/typeonce-dev/effect-machine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/effect-machine-release .claude/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .claude/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-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 typeonce-dev/effect-machine --skill effect-machine-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install typeonce-dev/effect-machine effect-machine-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/typeonce-dev/effect-machine.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/effect-machine-release .agents/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .agents/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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 typeonce-dev/effect-machine --skill effect-machine-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install typeonce-dev/effect-machine effect-machine-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/typeonce-dev/effect-machine.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/effect-machine-release .cursor/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .cursor/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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/typeonce-dev/effect-machine.git --path .agents/skills/effect-machine-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 typeonce-dev/effect-machine --skill effect-machine-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install typeonce-dev/effect-machine effect-machine-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/typeonce-dev/effect-machine.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/effect-machine-release .gemini/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .gemini/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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 typeonce-dev/effect-machine effect-machine-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 typeonce-dev/effect-machine --skill effect-machine-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/typeonce-dev/effect-machine.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/effect-machine-release .github/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .github/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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 typeonce-dev/effect-machine --skill effect-machine-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 typeonce-dev/effect-machine effect-machine-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/typeonce-dev/effect-machine.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/effect-machine-release .opencode/skills/effect-machine-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 "effect-machine-release" agent skill from https://github.com/typeonce-dev/effect-machine/tree/main/.agents/skills/effect-machine-release into .opencode/skills/effect-machine-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "effect-machine-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
effect-machine-release- GitHub stars
- 209
- Token cost
- ~916 tokens
- SKILL.md length
- 470 words
- Files
- 2
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run the complete Effect Machine implementation and release workflow in this repository.
- Works in 5 steps: After the feature merge, inspect the… → Fetch main and wait for the Changesets… → Confirm the release pull request's head… → …
- Explicitly requests the effect-machine-release workflow and wants a change implemented
- SKILL.md covers Ship the feature pull request, Find the release pull request, Validate and merge the release and Verify publication
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Effect Machine Release is an agent skill from typeonce-dev/effect-machine. Run the complete Effect Machine implementation and release workflow in this repository. Use only when the user explicitly requests the effect-machine-release workflow and wants a change implemented, validated, merged, included in the Changesets version pull request, and published. Do not use when the requested endpoint is only a feature pull request or merge to main.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Pull requests. The repository describes itself as: Schema-first state machines and statecharts for Effect. The licence is MIT.
When your agent uses it
- Explicitly requests the effect-machine-release workflow and wants a change implemented
- Included in the Changesets version pull request
- The requested endpoint is only a feature pull request
Example prompts
- “/effect-machine-release”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- After the feature merge, inspect the current .github/workflows/release.yml; follow the repository's actual Changesets and publish workflow…
- Fetch main and wait for the Changesets action to create or update its pull request. Identify it by the expected base, bot author, and…
- Confirm the release pull request's head includes the feature merge. Continue waiting if an older run or head revision does not yet contain…
- Inspect the complete diff. Verify the consumed changeset appears in the generated package version and changelog, the migration text…
- Aggregated release entries are allowed only when they correspond to changesets already merged into the base. Do not merge arbitrary code…
What it can do on your machine
Read from SKILL.md and the folder at commit 939825e. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Effect Machine Release loads about 916 tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 470 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 typeonce-dev/effect-machine at commit 939825e, republished under its MIT licence (© typeonce-dev). 470 words, ~916 tokens.
Download SKILL.mdSave it as
.claude/skills/effect-machine-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- effect-machine-release
- description
- Run the complete Effect Machine implementation and release workflow in this repository. Use only when the user explicitly requests the effect-machine-release workflow and wants a change implemented, validated, merged, included in the Changesets version pull request, and published. Do not use when the requested endpoint is only a feature pull request or merge to main.
- disable-model-invocation
- true
Effect Machine Release
This skill applies only to the Effect Machine repository. Accept an explicit request to use effect-machine-release by name or through the host's supported skill selection or command syntax. Discussing or editing this skill does not invoke its shipping workflow.
Ship the requested change through its feature pull request, the bot-owned Changesets version pull request, and the resulting publish workflow. Treat invocation as authorization to merge both validated pull requests; it does not authorize bypassing protections or merging unrelated, unverified work.
Ship the feature pull request
Before acting, read ../effect-machine-pr/SKILL.md completely and follow its entire implementation-to-merge workflow. Review the changeset before merging the feature pull request so its level and published text will not need repair later.
Find the release pull request
- After the feature merge, inspect the current
.github/workflows/release.yml; follow the repository's actual Changesets and publish workflow rather than assuming it is unchanged. - Fetch
mainand wait for the Changesets action to create or update its pull request. Identify it by the expected base, bot author, andchangeset-release/mainhead branch, not by title alone. - Confirm the release pull request's head includes the feature merge. Continue waiting if an older run or head revision does not yet contain it.
- Inspect the complete diff. Verify the consumed changeset appears in the generated package version and changelog, the migration text remains accurate, and no major version is introduced before 1.0.
- Aggregated release entries are allowed only when they correspond to changesets already merged into the base. Do not merge arbitrary code changes or an untrusted lookalike pull request.
Show full SKILL.md (207 more words)Show less
Validate and merge the release
- Monitor every required check on the current release head. If the bot updates the branch, restart the review and wait for checks on the new head.
- Treat versioning, changelog, packaging, correctness, and performance failures as blockers. Do not edit generated release output merely to bypass the source of a failure.
- Merge the release pull request only when its identity and contents are verified, it is current and mergeable, and all required checks are green.
- Verify the release merge commit on
origin/mainand confirm the release pull request is closed as merged.
Verify publication
- Monitor the release workflow triggered by the release merge. Distinguish the Changesets/version pull request from actual package publication.
- Confirm the Changesets action reports publication, the expected package version and tag exist, and any triggered website deployment succeeds.
- Report the feature pull request, release pull request, merge commits, released version, and publication status.
Keep waiting through normal bot and CI latency and provide concise progress updates. Do not stop merely because the release pull request has not appeared yet. If environment approval, credentials, repository protection, malformed aggregated content, or an external outage requires new authority, report the exact blocker without weakening the workflow.
© typeonce-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/effect-machine-release of typeonce-dev/effect-machine.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 939825e
Compare with similar skills
Effect Machine 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 |
|---|---|---|---|---|---|---|
| Effect Machine Release this skilltypeonce-dev/effect-machine | 209 | — | ~916 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
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.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from typeonce-dev/effect-machine
Effect Machine PR
typeonce-dev/effect-machine
Run the complete Effect Machine implementation-to-merge workflow in this repository.
Related
Categories
Questions about Effect Machine Release
What does Effect Machine Release do?
Run the complete Effect Machine implementation and release workflow in this repository. Effect Machine Release is an agent skill from typeonce-dev/effect-machine. Run the complete Effect Machine implementation and release workflow in this repository.
When should I use Effect Machine Release?
Effect Machine Release fits situations like: explicitly requests the effect-machine-release workflow and wants a change implemented; included in the Changesets version pull request; the requested endpoint is only a feature pull request.
How do I install Effect Machine Release in Claude Code?
Run `npx skills add typeonce-dev/effect-machine --skill effect-machine-release -a claude-code`. Or copy the skill folder (.agents/skills/effect-machine-release in typeonce-dev/effect-machine) into .claude/skills/effect-machine-release in your project. Claude Code loads it when a task matches its description.
How do I install Effect Machine Release in Codex?
Run `npx skills add typeonce-dev/effect-machine --skill effect-machine-release -a codex`. Or copy the skill folder (.agents/skills/effect-machine-release in typeonce-dev/effect-machine) into .agents/skills/effect-machine-release in your project. Codex loads it when a task matches its description.
Can I use Effect Machine 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 typeonce-dev/effect-machine --skill effect-machine-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/effect-machine-release, .gemini/skills/effect-machine-release, .github/skills/effect-machine-release and .opencode/skills/effect-machine-release in your project.
What does Effect Machine Release need to run?
SKILL.md names no scripts, command-line tools or credentials: Effect Machine Release is instructions for the agent only.
Does Effect Machine Release access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Effect Machine 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 Effect Machine Release use?
Effect Machine 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 Effect Machine Release use?
About 916 tokens (SKILL.md is roughly 3.7k 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 Effect Machine Release?
Skills that share tags, products or a category with Effect Machine Release: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Effect Machine Release?
typeonce-dev (a GitHub organization) maintains it in typeonce-dev/effect-machine, which has 209 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 2, 2026.
Source: typeonce-dev/effect-machine on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.