yeet-release
Handles patch release workflows for yeet, including documentation updates and tag verification.
Install
mkdir -p .claude/skills/yeet-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12535" && unzip -o skill.zip -d .claude/skills/yeet-release && rm skill.zipInstalls to .claude/skills/yeet-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when preparing, validating, tagging, or pushing a yeet patch release.Key capabilities
- →Find the latest patch version
- →Update `website/docs/changelog.mdx`
- →Commit and push website changes
- →Commit the updated `website` submodule pointer
- →Create an annotated tag
- →Land the release commit on `origin/main`
How it works
The skill identifies the next patch version, updates the changelog, commits website changes and the submodule pointer, creates an annotated tag, and lands the commit on `origin/main`.
Inputs & outputs
When to use yeet-release
- →Releasing a patch version
- →Updating release documentation
- →Validating release tags
About this skill
Yeet Release
Use this skill for release work. Follow root AGENTS.md exactly.
Patch Release Flow
- Find the latest
vX.Y.Ztag and choose the next patch version. - Update
website/docs/changelog.mdxwith a date section, version heading, and 1-3 user-facing bullets. Follow.codex/skills/yeet-docs/SKILL.mdfor changelog wording: the latest version must stand alone for users, and corrective release plumbing must not be the release note. - Commit and push the website changes inside
website/. - Commit the updated
websitesubmodule pointer in the root repo. - Create an annotated tag with message equal to the version:
git tag -a vX.Y.Z -m "vX.Y.Z"
- Land the release commit on
origin/mainthrough the rootAGENTS.mdfinish-to-main flow, then push the tag.
Verification
git status --short --branch
git -C website status --short --branch
git rev-parse HEAD:website
git -C website rev-parse HEAD
git tag --list 'v*' --sort=-version:refname | sed -n '1,5p'
git ls-remote --tags origin vX.Y.Z
Do not commit, tag, or push without explicit user authorization.
When not to use it
- →When not preparing a yeet patch release
- →When not validating a yeet patch release
- →When not tagging or pushing a yeet patch release
Limitations
- →Requires following root `AGENTS.md` exactly
- →Does not commit, tag, or push without explicit user authorization
- →Changelog wording must follow `.codex/skills/yeet-docs/SKILL.md`
How it compares
This workflow specifically manages the `website` submodule and enforces a particular changelog format, which is distinct from a generic release process.
Compared to similar skills
yeet-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| yeet-release (this skill) | 0 | 1mo | Review | Intermediate |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.