Agent skill

Full Release

Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands.

MITAuto-check passedDevelopment

Install Full Release

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a claude-code

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

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release --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/mrajaeim/image-pipes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/full-release .claude/skills/full-release && 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/

Paste into Claude Code

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .claude/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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

$skill-installer install https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release

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

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mrajaeim/image-pipes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/full-release .agents/skills/full-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .agents/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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.

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mrajaeim/image-pipes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/full-release .cursor/skills/full-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .cursor/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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

$ gemini skills install https://github.com/mrajaeim/image-pipes.git --path .cursor/skills/full-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mrajaeim/image-pipes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/full-release .gemini/skills/full-release && rm -rf skills-src

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

Paste into Gemini CLI

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .gemini/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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.

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release

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

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mrajaeim/image-pipes.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/full-release .github/skills/full-release && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .github/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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.

skills CLI

$ npx skills add mrajaeim/image-pipes --skill full-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mrajaeim/image-pipes full-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mrajaeim/image-pipes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/full-release .opencode/skills/full-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "full-release" agent skill from https://github.com/mrajaeim/image-pipes/tree/main/.cursor/skills/full-release into .opencode/skills/full-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "full-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: full-release
GitHub stars: 125
Token cost: ~1.3k tokens
SKILL.md length: 480 words
Files: 1
Skills in repo: 1
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands.

Works in 7 steps: Inspect state → Update CHANGELOG.md → Commit remaining release files → …
The user asks to release
SKILL.md covers Preconditions, Push policy (manual), Workflow and Desktop version notes, plus 1 more section
Calls git, uv and npm

What it does

Full Release is an agent skill from mrajaeim/image-pipes. Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands. Use when the user asks to release, cut a version, tag a release, sync commits and tags, or update the changelog for a version.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes, Commit messages and Technical writing. It works with OpenCV. The repository describes itself as: Image Pipeline Playground. The licence is MIT.

When your agent uses it

The user asks to release
Sync commits and tags
Update the changelog for a version

Example prompts

“/full-release”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Inspect state
Update CHANGELOG.md
Commit remaining release files
Quality gates
Create annotated tag locally
Give user push commands
Verify (after user confirms push)

What it can do on your machine

Read from SKILL.md and the folder at commit 28951c9. 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:
- git
- uv
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, uv and npm, 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

Full Release loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 480 words of instructions outside code blocks.

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

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 mrajaeim/image-pipes at commit 28951c9, republished under its MIT licence (© mrajaeim). 480 words, ~1,289 tokens.

Download SKILL.mdSave it as .claude/skills/full-release/SKILL.md (or your agent's skills folder).

name: full-release
description: Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v* tag, and give the user manual push commands. Use when the user asks to release, cut a version, tag a release, sync commits and tags, or update the changelog for a version.
disable-model-invocation: true

Full Release

End-to-end release for this repo: changelog → commits → manual push → tag → manual push tag.

Preconditions

Confirm with the user before tagging:

Version — e.g. 0.2.1 (tag will be v0.2.1)
Branch — usually main, clean enough to release

Do not move or delete a tag that already exists on the remote / has a GitHub Release. If the release is already cut, bump to the next patch/minor instead.

Follow .cursor/rules/incremental-commits.mdc for any commits. Prefer small conventional commits; do not dump unrelated WIP into the release commit.

Push policy (manual)

The agent never pushes. This environment often lacks GitHub SSH/HTTPS credentials.

After commits (and optional local tag), print copy-paste commands for the user. Wait for them to say they pushed, then verify.

Workflow

Copy and track:

Release Progress:
- [ ] 1. Inspect state
- [ ] 2. Update CHANGELOG.md
- [ ] 3. Commit remaining release files
- [ ] 4. Quality gates (if code changed)
- [ ] 5. Create annotated tag locally
- [ ] 6. Give user push commands (commits + tag)
- [ ] 7. After user confirms push — verify

1. Inspect state

bash

git status -sb
git fetch origin --tags
git log --oneline origin/main..HEAD
git tag -l "v*"
git describe --tags --abbrev=0

If git fetch fails (auth), continue with local state and note that remote verification may be limited.

Note uncommitted files, unpushed commits, and whether vX.Y.Z already exists locally or on origin.

2. Update CHANGELOG.md

Keep a Changelog + SemVer. File: CHANGELOG.md.

Move [Unreleased] notes into a new section:

markdown

## [Unreleased]

## [X.Y.Z] - YYYY-MM-DD

### Added
### Changed
### Fixed
### Removed

Write bullets from git log <previous-tag>..HEAD (group by Added / Changed / Fixed / Removed / Documentation). Prefer user-facing language over raw commit subjects.
Update compare links at the bottom:

markdown

[Unreleased]: https://github.com/mrajaeim/image-pipes/compare/vX.Y.Z...HEAD
[X.Y.Z]: https://github.com/mrajaeim/image-pipes/releases/tag/vX.Y.Z
[previous]: https://github.com/mrajaeim/image-pipes/releases/tag/vPREV

Leave [Unreleased] empty (heading only) after cutting the release.

3. Commit remaining release files

Commit only what belongs in the release (changelog, version-sync script, workflow tweaks, docs). Use incremental conventional commits, for example:

text

docs: finalize vX.Y.Z changelog
chore(desktop): sync installer version from git tag

Do not stage secrets or unrelated dirty files.

4. Quality gates

If backend/frontend code changed in this release slice:

Backend: uv run ruff check and uv run pytest from backend/
Frontend: npm run typecheck and npm run lint from frontend/

Skip full gates when the only change is CHANGELOG.md / docs.

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

5. Create annotated tag locally

Tag the commit that includes the changelog:

bash

git tag -a vX.Y.Z -m "vX.Y.Z"

Rules:

Tag format: v + semver (v0.2.1)
Annotated tags only (-a)
Never retag / force-push an existing published tag
Creating the tag locally is fine; pushing it is the user's job

6. Give user push commands

Print a ready-to-run block (fill in the real version). Do not run git push yourself.

bash

# Push commits
git push -u origin HEAD

# Push tag (triggers desktop release CI)
git push origin vX.Y.Z

If the tag was not created yet, include create + push:

bash

git push -u origin HEAD
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z

Tell the user: after pushing, reply so verification can run.

Pushing v* triggers .github/workflows/desktop.yml (build + GitHub Release). Desktop installer version is synced from the tag inside scripts/build-desktop.mjs (v0.2.1 → 0.2.1).

7. Verify (after user confirms push)

bash

git status -sb
git log -1 --oneline
git show vX.Y.Z --oneline -s
git fetch origin --tags   # if auth works

Report:

Changelog section version + date
Commit SHA
Tag name
Whether main matches origin/main (when fetch works)
Release URL: https://github.com/mrajaeim/image-pipes/releases/tag/vX.Y.Z

Desktop version notes

electron-builder reads desktop/package.json version
Tag builds: scripts/build-desktop.mjs sets that version from GITHUB_REF / nearest tag / IMAGE_PIPES_VERSION
Do not hand-edit desktop/package.json version for tagged releases unless the user asks

Anti-patterns

Agent running git push (always manual)
Force-updating a tag that already has a GitHub Release
Mixing feature WIP with the release/changelog commit
Empty or missing changelog section for the new version
Lightweight tags (git tag vX.Y.Z without -a)

Files

Just SKILL.md in .cursor/skills/full-release of mrajaeim/image-pipes.

Open the folder on GitHubat commit 28951c9

Compare with similar skills

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

Full Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Full Release this skillmrajaeim/image-pipes	125	—	~1.3k	Automated safety check: Pass	MIT	6 days ago
Plain EnglishFallout-build/Fallout	165	—	~2k	Automated safety check: Pass	Custom licence	5 days ago
Documentationaiskillstore/marketplace	430	1 repos	~2.7k	Automated safety check: Pass	None	yesterday
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
Git Workflow and Versioningaddyosmani/agent-skills	103k	2 repos	~3.5k	Automated safety check: Notes	MIT	5 days ago
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Plain English
Fallout-build/Fallout
Write clear, plain English for developer-facing prose aimed at an international audience.
165 GitHub stars~2k tokensUpdated 5 days ago
DevelopmentAuto-check passed
Documentation
aiskillstore/marketplace
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.
430 GitHub starsUsed in 1 repo~2.7k tokens
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
3.5k GitHub stars~839 tokensUpdated yesterday
DevelopmentAuto-check passed

Works with

OpenCV

Questions about Full Release

What does Full Release do?

Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands. Full Release is an agent skill from mrajaeim/image-pipes. Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands.

When should I use Full Release?

Full Release fits situations like: the user asks to release; sync commits and tags; update the changelog for a version.

How do I install Full Release in Claude Code?

Run `npx skills add mrajaeim/image-pipes --skill full-release -a claude-code`. Or copy the skill folder (.cursor/skills/full-release in mrajaeim/image-pipes) into .claude/skills/full-release in your project. Claude Code loads it when a task matches its description.

How do I install Full Release in Codex?

Run `npx skills add mrajaeim/image-pipes --skill full-release -a codex`. Or copy the skill folder (.cursor/skills/full-release in mrajaeim/image-pipes) into .agents/skills/full-release in your project. Codex loads it when a task matches its description.

Can I use Full 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 mrajaeim/image-pipes --skill full-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/full-release, .gemini/skills/full-release, .github/skills/full-release and .opencode/skills/full-release in your project.

What does Full Release need to run?

Going by SKILL.md and its folder, Full Release needs the command-line tools its instructions call (git, uv and npm).

Does Full Release access the network?

SKILL.md contains no URLs. Its commands use git, uv and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Full 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 Full Release use?

Full 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 Full Release use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Full Release?

Skills that share tags, products or a category with Full Release: Plain English (Fallout-build/Fallout, 165 stars), Documentation (aiskillstore/marketplace, 430 stars), React Router Release Notes Prep (remix-run/react-router, 57k stars) and Git Workflow and Versioning (addyosmani/agent-skills, 103k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Full Release?

mrajaeim (a GitHub user) maintains it in mrajaeim/image-pipes, which has 125 GitHub stars. The repository was last updated on October 2, 2026.

Source: mrajaeim/image-pipes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Full Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Full Release

Preconditions

Push policy (manual)

Workflow

1. Inspect state

2. Update CHANGELOG.md

3. Commit remaining release files

4. Quality gates

5. Create annotated tag locally

6. Give user push commands

7. Verify (after user confirms push)

Desktop version notes

Anti-patterns

Files

Compare with similar skills

Similar skills

Plain English

Documentation

React Router Release Notes Prep

Git Workflow and Versioning

Verdaccio Pull Request Workflow

Commitizen

Related

Questions about Full Release