Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication.
$ npx skills add compozy/compozy --skill releasepr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install compozy/compozy releasepr --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/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/releasepr .claude/skills/releasepr && 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 "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .claude/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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/compozy/compozy/tree/main/.agents/skills/releaseprType 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 compozy/compozy --skill releasepr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install compozy/compozy releasepr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/releasepr .agents/skills/releasepr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .agents/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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 compozy/compozy --skill releasepr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install compozy/compozy releasepr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/releasepr .cursor/skills/releasepr && 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 "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .cursor/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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/compozy/compozy.git --path .agents/skills/releasepr--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 compozy/compozy --skill releasepr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install compozy/compozy releasepr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/releasepr .gemini/skills/releasepr && 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 "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .gemini/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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 compozy/compozy releaseprInstalls 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 compozy/compozy --skill releasepr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/releasepr .github/skills/releasepr && 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 "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .github/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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 compozy/compozy --skill releasepr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install compozy/compozy releasepr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/releasepr .opencode/skills/releasepr && 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 "releasepr" agent skill from https://github.com/compozy/compozy/tree/main/.agents/skills/releasepr into .opencode/skills/releasepr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasepr", 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.
releaseprAdopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication.
Releasepr is an agent skill from compozy/compozy. Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `references/commands.md`, `references/configuration.md` and `references/published-release-repair.md`).
It sits in Development. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit c15729c. It shows what the files ask for, not the result of running them.
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.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gobashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
RELEASE_TOKENGITHUB_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Releasepr loads about 1.9k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 774 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.
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); the scripts in this folder are not scanned.
The full file from compozy/compozy at commit c15729c, republished under its MIT licence (© compozy). 774 words, ~1,857 tokens.
.claude/skills/releasepr/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.pr-release (Go module github.com/compozy/releasepr) automates the GitHub
release workflow: it inspects conventional commits, computes the next semantic
version, generates a git-cliff changelog, opens or updates a release pull
request, and — once that PR merges — drives a GoReleaser production release.
This skill is for agents working in a consuming project that depends on
pr-release. It is not for hacking on the pr-release Go source.
The detail that makes setup and usage correct lives in references/. The
inline content in this file is a dispatcher and a tripwire, not the
contract. Match the task in the router, then read the listed file in full
before acting.
Match the task to the row. Read the listed file(s) in full before producing output or running commands. They are load-bearing, not appendices.
| Task | MUST read |
|---|---|
| Set up pr-release in a repo for the first time | references/setup.md + references/configuration.md |
Create or change .pr-release.yaml / env vars / artifacts | references/configuration.md |
| Run or script a CLI command, choose flags | references/commands.md |
| Understand or debug the release lifecycle / CI behavior | references/release-workflow.md |
| Write commit messages or add custom release notes | references/release-notes.md |
| Correct notes for an already-published release | references/published-release-repair.md + references/release-workflow.md |
| A release step failed or behaved unexpectedly | references/troubleshooting.md |
references/setup.md — install options (prebuilt tarball, go install), the
GitHub token requirement, owner/repo auto-detection order, copying the
workflow template, and the first dry-run.references/configuration.md — every .pr-release.yaml field, defaults,
validation rules, the full environment-variable alias matrix, and
release_artifacts constraints.references/commands.md — pr-release, plan, release-body, dry-run, add-note, version:
every flag and its exact behavior.references/release-workflow.md — the end-to-end lifecycle: which commits
trigger what, release branch/PR naming, dry-run checks, and how a merge
becomes a production release.references/release-notes.md — conventional-commit prefixes that drive the
version bump, the add-note workflow, and .release-notes/ archival.references/troubleshooting.md — symptom → cause → fix for the common
failures (token format, owner/repo detection, "no release PR produced", etc.).Confirm the dependency. Verify the project actually uses pr-release
(a release workflow invoking pr-release, a .pr-release.yaml, or an
explicit request). If it does not, this skill does not apply.
Verify wiring before changing anything. Run the read-only helper from
the consuming repo root:
bash skills/releasepr/scripts/check-setup.sh
It reports PASS/WARN/FAIL for the binary, token, config file, owner/repo
resolution, conventional commits, and the workflow file. It only inspects —
it never writes, pushes, or calls mutating APIs.
Set up (if check-setup reports missing pieces). Copy
skills/releasepr/assets/release.yml.template into
.github/workflows/ and skills/releasepr/assets/pr-release.yaml.template
to .pr-release.yaml, then adjust.
STOP. Read references/setup.md and references/configuration.md in full
before installing pr-release or editing any config. The asset templates and
the bullets here are starting points, not the contract — defaults, validation
ranges, and the env-var matrix are only complete in those files.
Run or script a command. The de-facto standard CI invocation across
every observed consumer is
pr-release pr-release --force --enable-rollback --ci-output — install via
go run "<module>@<pinned tag>". --force makes it idempotent, not "release
with no changes".
STOP. Read references/commands.md in full before running pr-release,
plan, release-body, dry-run, or add-note, or adding any flag to a script. The flag list
here is a tripwire; semantics (e.g. --rollback, --session-id,
--skip-pr) are only correct in that file.
Reason about lifecycle / CI. Before explaining why a release did or did
not happen, or editing the workflow.
STOP. Read references/release-workflow.md in full before diagnosing CI
behavior or modifying the release workflow. Trigger rules and the
merge → production-release path are only accurate there.
Diagnose a failure.
STOP. Read references/troubleshooting.md in full before proposing a fix
for any pr-release error. Match the exact error string to its row.
Conventional-commit prefixes drive the version bump — wrong prefixes mean wrong versions or "no changes":
fix: → patch · feat: → minor · feat!: / BREAKING CHANGE: → major.release: or ci(release): merged to the
default branch is what triggers the production release — do not hand-write
such commits.Merge pull request commits are skipped by the release-PR job.STOP. Read references/release-notes.md and references/release-workflow.md
in full before advising on commit messages or release timing. The three
bullets above are tripwires, not the rule set.
Setup prerequisites that cause the most real-world failures:
fetch-depth: 0, fetch-tags: true)
or the version is wrong.git-cliff MUST be installed in the runner; pr-release shells out to it.RELEASE_TOKEN (PAT/App), not the default GITHUB_TOKEN,
or downstream checks won't dispatch.STOP. Read references/setup.md in full before installing or wiring
pr-release in any repository. These three are tripwires, not the setup
contract.
scripts/check-setup.sh — read-only consumer-repo wiring verifier. Safe
to run anytime; performs no writes, pushes, or mutating API calls.assets/pr-release.yaml.template — copy-in starter config (every field
commented).assets/release.yml.template — copy-in starter GitHub Actions release
workflow for a consuming repo.© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (scripts, references, assets) in .agents/skills/releasepr of compozy/compozy.
Open the folder on GitHubat commit c15729c
Releasepr 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 |
|---|---|---|---|---|---|---|
| Releasepr this skillcompozy/compozy | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
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.
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
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.
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
compozy/compozy
Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.
compozy/compozy
Go test-shape discipline for Compozy. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.
compozy/compozy
Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.
compozy/compozy
Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.
Categories
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Releasepr is an agent skill from compozy/compozy. Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication.
Releasepr fits situations like: development work in your project.
Run `npx skills add compozy/compozy --skill releasepr -a claude-code`. Or copy the skill folder (.agents/skills/releasepr in compozy/compozy) into .claude/skills/releasepr in your project. Claude Code loads it when a task matches its description.
Run `npx skills add compozy/compozy --skill releasepr -a codex`. Or copy the skill folder (.agents/skills/releasepr in compozy/compozy) into .agents/skills/releasepr in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill releasepr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releasepr, .gemini/skills/releasepr, .github/skills/releasepr and .opencode/skills/releasepr in your project.
Going by SKILL.md and its folder, Releasepr needs a shell for the scripts in its folder, the command-line tools its instructions call (go and bash) and credentials named RELEASE_TOKEN and GITHUB_TOKEN. Our summary lists: A Bash shell; A credential in RELEASE_TOKEN; A credential in GITHUB_TOKEN.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Releasepr is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Releasepr: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k 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.
compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,791 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.
Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.