Agent skill

Releasepr

by compozy in compozy/compozy

Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication.

MITAuto-check passedDevelopment

Install Releasepr

skills CLI
$ npx skills add compozy/compozy --skill releasepr -a claude-code

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

GitHub CLI
$ gh skill install compozy/compozy releasepr --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/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/releasepr .claude/skills/releasepr && 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
releasepr
GitHub stars
2.8k
Token cost
~1.9k tokens
SKILL.md length
774 words
Files
11 (incl. scripts, references, assets)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication.

  • Works in 6 steps: Confirm the dependency. Verify the… → Verify wiring before changing anything.… → Set up (if check-setup reports missing… → …
  • Development work in your project
  • SKILL.md covers Required Reading Router, Reference Index, Operating loop and Gist tripwires (incomplete on…, plus 1 more section
  • Runs Shell scripts from its folder; calls go and bash; needs RELEASE_TOKEN and GITHUB_TOKEN

What it does

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.

When your agent uses it

  • Development work in your project

Example prompts

  • “/releasepr”

Requirements

  • A Bash shell
  • A credential in RELEASE_TOKEN
  • A credential in GITHUB_TOKEN

Workflow steps

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

  1. Confirm the dependency. Verify the project actually uses pr-release
  2. Verify wiring before changing anything. Run the read-only helper from
  3. Set up (if check-setup reports missing pieces). Copy
  4. Run or script a command. The de-facto standard CI invocation across
  5. Reason about lifecycle / CI. Before explaining why a release did or did
  6. Diagnose a failure.

What it can do on your machine

Read from SKILL.md and the folder at commit c15729c. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • go
    • bash

    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 these keys or tokens, usually read from environment variables:

    • RELEASE_TOKEN
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from compozy/compozy at commit c15729c, republished under its MIT licence (© compozy). 774 words, ~1,857 tokens.

Download SKILL.mdSave it as .claude/skills/releasepr/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
releasepr
description
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.
license
MIT
metadata.domain
release-automation
metadata.triggers
pr-release, releasepr, release PR, release plan, beta release, changelog, conventional commits, git-cliff, GoReleaser, .pr-release.yaml, add-note, dry-run
metadata.role
specialist
metadata.scope
integration

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.

Required Reading Router

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.

TaskMUST read
Set up pr-release in a repo for the first timereferences/setup.md + references/configuration.md
Create or change .pr-release.yaml / env vars / artifactsreferences/configuration.md
Run or script a CLI command, choose flagsreferences/commands.md
Understand or debug the release lifecycle / CI behaviorreferences/release-workflow.md
Write commit messages or add custom release notesreferences/release-notes.md
Correct notes for an already-published releasereferences/published-release-repair.md + references/release-workflow.md
A release step failed or behaved unexpectedlyreferences/troubleshooting.md

Reference Index

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

Operating loop

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

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

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

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

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

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

Show full SKILL.md (196 more words)Show less

Gist tripwires (incomplete on purpose)

Conventional-commit prefixes drive the version bump — wrong prefixes mean wrong versions or "no changes":

  • fix: → patch · feat: → minor · feat!: / BREAKING CHANGE: → major.
  • A commit subject starting with release: or ci(release): merged to the default branch is what triggers the production release — do not hand-write such commits.
  • Bot commits and 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:

  • Checkout MUST be unshallow with tags (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.
  • Use a dedicated 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.

Bundled resources

  • 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

Files

SKILL.md and 10 other files (scripts, references, assets) in .agents/skills/releasepr of compozy/compozy.

  • SKILL.md
  • assets/pr-release.yaml.template
  • assets/release.yml.template
  • references/commands.md
  • references/configuration.md
  • references/published-release-repair.md
  • references/release-notes.md
  • references/release-workflow.md
  • references/setup.md
  • references/troubleshooting.md
  • scripts/check-setup.sh

Open the folder on GitHubat commit c15729c

Compare with similar skills

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.

Releasepr compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Releasepr this skillcompozy/compozy2.8k—~1.9kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • 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.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    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.

    10k GitHub starsUsed in 25 repos~4.2k 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
  • 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.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    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.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from compozy/compozy

All 47 skills in this repo
  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed
  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed
  • Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed
  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Categories

Questions about Releasepr

What does Releasepr do?

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.

When should I use Releasepr?

Releasepr fits situations like: development work in your project.

How do I install Releasepr in Claude Code?

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.

How do I install Releasepr in Codex?

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.

Can I use Releasepr 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 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.

What does Releasepr need to run?

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.

Does Releasepr 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 Releasepr 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Releasepr use?

Releasepr is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Releasepr use?

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.

What are the alternatives to Releasepr?

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.

Who maintains Releasepr?

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.