release — community release, ziglint, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for AI Agents like Cursor, Windsurf, and Claude Code needing automated version control and release notes management through opinionated linting. Publishes ziglint releases. Use when releasing, versioning, tagging, or publishing a new version.

rockorager rockorager
[0]
[0]
Updated: 3/11/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Ideal for AI Agents like Cursor, Windsurf, and Claude Code needing automated version control and release notes management through opinionated linting. Publishes ziglint releases. Use when releasing, versioning, tagging, or publishing a new version.

Core Value

Empowers agents to manage releases efficiently using git tags, automated commit checks, and markdown-based release notes in files like `docs/releases/vX.Y.Z.md`, streamlining the development process with tools like `git tag` and `git push`.

Ideal Agent Persona

Ideal for AI Agents like Cursor, Windsurf, and Claude Code needing automated version control and release notes management through opinionated linting.

↓ Capabilities Granted for release

Automating version updates in `build.zig.zon`
Generating release notes in markdown format
Streamlining git workflow with `git tag` and `git push --tags`

! Prerequisites & Limits

  • Requires git version control system
  • Specific folder structure like `docs/releases/`
  • Manual update of version in `build.zig.zon` and creation of release notes markdown files

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is release?

Ideal for AI Agents like Cursor, Windsurf, and Claude Code needing automated version control and release notes management through opinionated linting. Publishes ziglint releases. Use when releasing, versioning, tagging, or publishing a new version.

How do I install release?

Run the command: npx killer-skills add rockorager/ziglint. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for release?

Key use cases include: Automating version updates in `build.zig.zon`, Generating release notes in markdown format, Streamlining git workflow with `git tag` and `git push --tags`.

Which IDEs are compatible with release?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for release?

Requires git version control system. Specific folder structure like `docs/releases/`. Manual update of version in `build.zig.zon` and creation of release notes markdown files.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add rockorager/ziglint. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use release immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

release

Install release, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Releasing ziglint

Quick Release Checklist

  1. Update version in build.zig.zon
  2. Write release notes in docs/releases/vX.Y.Z.md
  3. Commit changes
  4. Tag and push: git tag vX.Y.Z && git push && git push --tags

Release Notes

Create a markdown file at docs/releases/vX.Y.Z.md (must match the tag name exactly).

Example for docs/releases/v0.1.0.md:

markdown
1## What's New
2
3- Initial release of ziglint
4- Zig linting and style checks
5
6## Breaking Changes
7
8None (initial release)
9
10## Installation
11
12```bash
13mise use github:rockorager/ziglint

If no release notes file exists, the release will use "Release vX.Y.Z" as the body.

## What Happens on Release

When you push a tag matching `v*`:

1. **Build job** - Cross-compiles on ubuntu-latest for:
   - `aarch64-macos`
   - `x86_64-linux`
   - `x86_64-windows`
2. **Release job** - Creates GitHub release with:
   - Tarballs (`.tar.gz`) for Unix platforms
   - Zip (`.zip`) for Windows
   - `checksums.txt` with SHA256 hashes
   - Release notes from `docs/releases/vX.Y.Z.md`

## Prerelease Tags

Tags containing `-` (e.g., `v0.1.0-beta`, `v0.2.0-rc1`) are automatically marked as prereleases on GitHub.

## Installing via mise

Users can install ziglint directly from GitHub releases:

```bash
mise use github:rockorager/ziglint

Related Skills

Looking for an alternative to release or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer