New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Effect Machine PR

by typeonce-dev in typeonce-dev/effect-machine

Run the complete Effect Machine implementation-to-merge workflow in this repository.

MITAuto-check passedDevelopment

Install Effect Machine PR

skills CLI
$ npx skills add typeonce-dev/effect-machine --skill effect-machine-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install typeonce-dev/effect-machine effect-machine-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-pr .claude/skills/effect-machine-pr && rm -rf skills-src

Use ~/.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/

Facts

Skill name
effect-machine-pr
GitHub stars
209
Token cost
~1.1k tokens
SKILL.md length
585 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Run the complete Effect Machine implementation-to-merge workflow in this repository.

  • Works in 5 steps: Read AGENTS.md and every instruction it… → Inspect the worktree and preserve all… → Use the base branch named by the user,… → …
  • Explicitly requests the effect-machine-pr workflow and wants a change implemented
  • SKILL.md covers Establish the baseline, Implement the complete change, Validate locally and Publish and merge
  • Calls pnpm

What it does

Effect Machine PR is an agent skill from typeonce-dev/effect-machine. Run the complete Effect Machine implementation-to-merge workflow in this repository. Use only when the user explicitly requests the effect-machine-pr workflow and wants a change implemented, validated, published as a pull request, checked in CI, and merged. Do not use for design, review, diagnosis, or implementation that should stop before publication.

Its SKILL.md is about 1.1k 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 Design review and critique and 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-pr workflow and wants a change implemented
  • Published as a pull request
  • Implementation that should stop before publication

Example prompts

  • “/effect-machine-pr”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md and every instruction it routes to before changing files.
  2. Inspect the worktree and preserve all user-owned changes. Never discard or overwrite unrelated work.
  3. Use the base branch named by the user, or main by default.
  4. Fetch the latest remote base. In its primary worktree, switch to the base and run a fast-forward-only pull. If the base is checked out in…
  5. Create a focused branch named after the change, using lowercase words separated by hyphens, unless the user specifies another name. Keep…

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

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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

Effect Machine PR loads about 1.1k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 585 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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). 585 words, ~1,110 tokens.

Download SKILL.mdSave it as .claude/skills/effect-machine-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
effect-machine-pr
description
Run the complete Effect Machine implementation-to-merge workflow in this repository. Use only when the user explicitly requests the effect-machine-pr workflow and wants a change implemented, validated, published as a pull request, checked in CI, and merged. Do not use for design, review, diagnosis, or implementation that should stop before publication.
disable-model-invocation
true

Effect Machine PR

This skill applies only to the Effect Machine repository. Accept an explicit request to use effect-machine-pr 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 a green, merged pull request. Treat invocation as authorization for the in-scope branch, commits, push, pull request, CI fixes, and final merge; it does not authorize unrelated changes, bypassing protections, or destructive recovery.

Establish the baseline

  1. Read AGENTS.md and every instruction it routes to before changing files.
  2. Inspect the worktree and preserve all user-owned changes. Never discard or overwrite unrelated work.
  3. Use the base branch named by the user, or main by default.
  4. Fetch the latest remote base. In its primary worktree, switch to the base and run a fast-forward-only pull. If the base is checked out in another worktree, branch directly from the freshly fetched origin/<base> commit instead.
  5. Create a focused branch named after the change, using lowercase words separated by hyphens, unless the user specifies another name. Keep branch names independent of the agent, editor, or provider.

Implement the complete change

  1. Inspect the relevant public API, internals, tests, documentation, and analogous Effect implementation before editing.
  2. Implement the long-term design, including generic and optimized semantics where applicable. Follow the Cluster ownership boundary in AGENTS.md.
  3. Add observable runtime tests, typetests, differential tests, JSDocs, README, and guide updates required to make the feature complete.
  4. Add a changeset when required. Use minor for a public addition or breaking change and patch for a compatible fix or implementation improvement. Never use major before 1.0.
  5. Keep the changeset user-facing: explain the resulting API and direct migration, not implementation history or external inspiration.

Validate locally

  1. Run pnpm check.
  2. Run pnpm perf:types for changes that affect the public TypeScript API or inference.
  3. Always run pnpm perf:runtime before publishing this full-lifecycle workflow. Treat the local run as a functional smoke test; the CI base-versus-PR comparison is authoritative.
  4. Fix every failure and repeat all affected checks. Treat correctness, type safety, runtime performance, and memory regressions as blockers.
  5. Audit the final diff, formatting, generated files, public terminology, changeset level, and working-tree scope.
Show full SKILL.md (210 more words)Show less

Publish and merge

  1. Stage only the intended files, commit with a concise outcome-oriented message, and confirm the worktree is clean.
  2. Fetch the remote base again before pushing. If it advanced materially, integrate it safely and repeat affected validation.
  3. Push the branch and open a ready pull request using the repository template. Record the changeset decision and validation without copying noisy local benchmark tables.
  4. Monitor every required check and type/runtime performance workflow. Inspect the base-versus-PR reports, not only the aggregate green status.
  5. Diagnose failures from their logs, implement in-scope fixes, rerun relevant local checks, push, and continue monitoring. Never weaken semantics, inference, tests, or thresholds to make CI pass.
  6. Merge only when the pull request is current, mergeable, and every required check is green. Use the repository's normal squash-and-branch-cleanup convention unless instructed otherwise.
  7. Verify the pull request's remote state even if the merge command reports a local worktree checkout error. Confirm the merge commit is present on origin/<base> and the remote feature branch was removed.

Keep the user informed during long checks. Do not stop at an open pull request or merely enable auto-merge. If repository protection, an approval, credentials, or an external outage prevents completion, exhaust safe checks and report the precise blocker.

© 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-pr of typeonce-dev/effect-machine.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 939825e

Compare with similar skills

Effect Machine PR 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.

Effect Machine PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Effect Machine PR this skilltypeonce-dev/effect-machine209—~1.1kAutomated safety check: PassMIT
Code Reviewgetsentry/skills1k3 repos~692Automated safety check: PassApache-2.0
Fix PR Design Notesdifferent-ai/openwork24k—~824Automated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Code Review

    getsentry/skills

    Official

    Perform code reviews following Sentry engineering practices.

    1k GitHub starsUsed in 3 repos~692 tokens
    DevelopmentAuto-check passed

  • Fix PR Design Notes

    different-ai/openwork

    Reads the advisory design review attached to a pull request's screenshots, fixes the flagged UI problems in product code, and proves each note is gone.

    24k GitHub stars~824 tokensUpdated today
    Frontend & DesignAuto-check passed

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • 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.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • 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.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

More from typeonce-dev/effect-machine

  • Effect Machine Release

    typeonce-dev/effect-machine

    Run the complete Effect Machine implementation and release workflow in this repository.

    209 GitHub stars~916 tokensUpdated 6 days ago
    Auto-check passed

Categories

Questions about Effect Machine PR

What does Effect Machine PR do?

Run the complete Effect Machine implementation-to-merge workflow in this repository. Effect Machine PR is an agent skill from typeonce-dev/effect-machine. Run the complete Effect Machine implementation-to-merge workflow in this repository.

When should I use Effect Machine PR?

Effect Machine PR fits situations like: explicitly requests the effect-machine-pr workflow and wants a change implemented; published as a pull request; implementation that should stop before publication.

How do I install Effect Machine PR in Claude Code?

Run `npx skills add typeonce-dev/effect-machine --skill effect-machine-pr -a claude-code`. Or copy the skill folder (.agents/skills/effect-machine-pr in typeonce-dev/effect-machine) into .claude/skills/effect-machine-pr in your project. Claude Code loads it when a task matches its description.

How do I install Effect Machine PR in Codex?

Run `npx skills add typeonce-dev/effect-machine --skill effect-machine-pr -a codex`. Or copy the skill folder (.agents/skills/effect-machine-pr in typeonce-dev/effect-machine) into .agents/skills/effect-machine-pr in your project. Codex loads it when a task matches its description.

Can I use Effect Machine PR 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-pr -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-pr, .gemini/skills/effect-machine-pr, .github/skills/effect-machine-pr and .opencode/skills/effect-machine-pr in your project.

What does Effect Machine PR need to run?

Going by SKILL.md and its folder, Effect Machine PR needs the command-line tools its instructions call (pnpm).

Does Effect Machine PR 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 PR 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 PR use?

Effect Machine PR 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 PR use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 PR?

Skills that share tags, products or a category with Effect Machine PR: Code Review (getsentry/skills, 1k stars), Fix PR Design Notes (different-ai/openwork, 24k stars), Finishing a Development Branch (obra/superpowers, 296k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Effect Machine PR?

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.