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.
Push a version tag and optionally create a GitHub release. An agent skill from spiriMirror/libuipc.
Install Push Tag
$ npx skills add spiriMirror/libuipc --skill push-tag -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spiriMirror/libuipc push-tag --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/spiriMirror/libuipc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/push-tag .claude/skills/push-tag && 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 "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .claude/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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/spiriMirror/libuipc/tree/main/.cursor/skills/push-tagType 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 spiriMirror/libuipc --skill push-tag -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spiriMirror/libuipc push-tag --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spiriMirror/libuipc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/push-tag .agents/skills/push-tag && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .agents/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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 spiriMirror/libuipc --skill push-tag -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spiriMirror/libuipc push-tag --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spiriMirror/libuipc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/push-tag .cursor/skills/push-tag && 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 "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .cursor/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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/spiriMirror/libuipc.git --path .cursor/skills/push-tag--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 spiriMirror/libuipc --skill push-tag -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spiriMirror/libuipc push-tag --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spiriMirror/libuipc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/push-tag .gemini/skills/push-tag && 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 "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .gemini/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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 spiriMirror/libuipc push-tagInstalls 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 spiriMirror/libuipc --skill push-tag -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/spiriMirror/libuipc.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/push-tag .github/skills/push-tag && 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 "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .github/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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 spiriMirror/libuipc --skill push-tag -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install spiriMirror/libuipc push-tag --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spiriMirror/libuipc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/push-tag .opencode/skills/push-tag && 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 "push-tag" agent skill from https://github.com/spiriMirror/libuipc/tree/main/.cursor/skills/push-tag into .opencode/skills/push-tag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "push-tag", 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
push-tag- GitHub stars
- 335
- Token cost
- ~480 tokens
- SKILL.md length
- 208 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Push a version tag and optionally create a GitHub release. An agent skill from spiriMirror/libuipc.
- Works in 4 steps: Verify branch → Determine tag version → Create and push tag → …
- Development work in your project
- SKILL.md covers Overview and Steps
- Calls git
What it does
Push Tag is an agent skill from spiriMirror/libuipc. Push a version tag and optionally create a GitHub release
Its SKILL.md is about 480 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. It works with GitHub. The repository describes itself as: A Modern Python and C++20 Library of Unified Incremental Potential Contact. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “/push-tag”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Verify branch
- Determine tag version
- Create and push tag
- Create release (if requested)
What it can do on your machine
Read from SKILL.md and the folder at commit 9c748a7. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Push Tag loads about 480 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 208 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 spiriMirror/libuipc at commit 9c748a7, republished under its Apache-2.0 licence (© spiriMirror). 208 words, ~480 tokens.
Download SKILL.mdSave it as
.claude/skills/push-tag/SKILL.md (or your agent's skills folder).- name
- push-tag
- description
- Push a version tag and optionally create a GitHub release
- disable-model-invocation
- true
Push Tag
Overview
Push a new tag to the upstream repository. Optionally create a GitHub release.
Steps
Verify branch
bash git branch --show-current- Must be on
mainbranch. If not, switch:git checkout main
- Must be on
Determine tag version
bash git tag --list- If user provides a tag: validate it doesn't exist and is greater than latest
- If no tag provided: auto-increment patch version (e.g.,
v1.2.3→v1.2.4)
Create and push tag
bash git tag <TAG> git push origin refs/tags/<TAG>Create release (if requested)
- Generate structured release notes (do not use
--generate-notes):- Get commits between previous tag and
<TAG>:bash git log <PREV_TAG>..<TAG> --pretty=format:'%s' --no-merges - Summarize and structure the changes into clear sections, e.g.:
- Features – new functionality
- Fixes – bug fixes
- Documentation – docs, examples, guides
- Refactor / Chore – internal changes, deps, tooling
- Write an overall summary at the top of the release notes: a short paragraph describing the key themes, goals, or highlights of this release compared to the previous one. This gives readers a quick understanding of what changed and why.
- Use concise, user-facing language. Group related changes. Avoid raw commit hashes or jargon unless helpful.
- Write notes to a temp file (e.g.
release_notes.md) and create the release:bash gh release create <TAG> --repo spiriMirror/libuipc --notes-file release_notes.md rm release_notes.md
- Get commits between previous tag and
- Generate structured release notes (do not use
Note: Always use --repo spiriMirror/libuipc to reference the upstream repository.
© spiriMirror, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/push-tag of spiriMirror/libuipc.
Open the folder on GitHubat commit 9c748a7
Compare with similar skills
Push Tag 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 |
|---|---|---|---|---|---|---|
| Push Tag this skillspiriMirror/libuipc | 335 | — | ~480 | Automated safety check: Pass | Apache-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | 1 repos | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
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.
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.
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
- Official
Summarise Ecosystem Results
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
More from spiriMirror/libuipc
All 16 skills in this repoGPU Optimization
spiriMirror/libuipc
GPU optimization workflow using uipc.profile, uipc.profile.nsight, and Nsight Compute CLI.
Review PR
spiriMirror/libuipc
Review a libuipc pull request end-to-end: checkout the PR, summarize changes, list files for the human reviewer, and perform a domain-aware AI review covering physics correctness, backend…
Xmake Workflow
spiriMirror/libuipc
Build and test the libuipc project using XMake. An agent skill from spiriMirror/libuipc.
Cmake Workflow
spiriMirror/libuipc
Build and test the libuipc project using CMake. An agent skill from spiriMirror/libuipc.
Document
spiriMirror/libuipc
Documentation style guide and rules for creating documentation
Fix Issue
spiriMirror/libuipc
Fix a GitHub issue with proper branch, testing, and PR workflow
Related
Works with
Categories
Questions about Push Tag
What does Push Tag do?
Push a version tag and optionally create a GitHub release. An agent skill from spiriMirror/libuipc. Push Tag is an agent skill from spiriMirror/libuipc.
When should I use Push Tag?
Push Tag fits situations like: development work in your project.
How do I install Push Tag in Claude Code?
Run `npx skills add spiriMirror/libuipc --skill push-tag -a claude-code`. Or copy the skill folder (.cursor/skills/push-tag in spiriMirror/libuipc) into .claude/skills/push-tag in your project. Claude Code loads it when a task matches its description.
How do I install Push Tag in Codex?
Run `npx skills add spiriMirror/libuipc --skill push-tag -a codex`. Or copy the skill folder (.cursor/skills/push-tag in spiriMirror/libuipc) into .agents/skills/push-tag in your project. Codex loads it when a task matches its description.
Can I use Push Tag 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 spiriMirror/libuipc --skill push-tag -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/push-tag, .gemini/skills/push-tag, .github/skills/push-tag and .opencode/skills/push-tag in your project.
What does Push Tag need to run?
Going by SKILL.md and its folder, Push Tag needs the command-line tools its instructions call (git).
Does Push Tag access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Push Tag 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 Push Tag use?
Push Tag is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Push Tag use?
About 480 tokens (SKILL.md is roughly 1.9k 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 Push Tag?
Skills that share tags, products or a category with Push Tag: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Push Tag?
spiriMirror (a GitHub organization) maintains it in spiriMirror/libuipc, which has 335 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 3, 2026.
Source: spiriMirror/libuipc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.