developer-release

Guides changeset-based releases, firewall log parsing, and breaking CLI change evaluation for gh-aw.

5.1k|530|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill developer-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-release
Source: https://github.com/github/gh-aw/tree/main/.github/skills/developer-release
Command: npx skills add https://github.com/github/gh-aw --skill developer-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the gh-aw CLI need consistent rules for versioning releases, classifying breaking changes, and analyzing firewall logs from agentic workflow runs, and this Skill consolidates those procedures into one reference.

Core Features & Use Cases

  • Changeset Release Management: Preview version bumps with the version command and execute releases that update CHANGELOG.md, delete processed changesets, commit, tag, and push.
  • Breaking Change Classification: Apply a decision tree covering command removal, flag renames, JSON output changes, default behavior shifts, and schema changes to assign major, minor, or patch changeset types.
  • Firewall Log Parsing: Parse 10-field Squid-style proxy logs, classify requests as allowed or denied by status codes and decisions, and produce console or JSON summaries.
  • Use Case: Before merging a PR that renames a CLI flag, consult the breaking change rules to determine it requires a major changeset with migration guidance, then run the release command to publish it.

Quick Start

Ask the agent to evaluate whether renaming a CLI flag is a breaking change and what changeset type the release requires.

Frequently Asked Questions about developer-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a release with the gh-aw changeset system?

Run node scripts/changeset.js release or make release from the main branch with a clean working tree. The script updates CHANGELOG.md, deletes processed changeset files, commits the changes, creates a git tag, and pushes it to the remote.

What counts as a breaking change for a CLI tool?

Breaking changes include removing or renaming commands and flags, changing JSON output structure, altering default behavior or exit codes for existing scenarios, and removing schema fields or making optional fields required. These require a major changeset and migration guidance.

How do I parse firewall logs from agentic workflow runs?

Firewall logs use a 10-field space-separated format including timestamp, client IP, domain, status, and proxy decision. Requests with status 200, 206, or 304 or decisions containing TCP_TUNNEL, TCP_HIT, or TCP_MISS are classified as allowed; 403, 407, or TCP_DENIED are denied.

Can I release without adding changeset files?

Yes, run node scripts/changeset.js release with no changesets present and it defaults to a patch release with a generic maintenance entry in CHANGELOG.md. You can also specify minor or major explicitly, or pass --yes to skip the confirmation prompt.

Is deprecating a CLI flag considered a breaking change?

No, deprecation is not breaking if the flag keeps working, prints a warning to stderr, and documents a migration path. The deprecated functionality must remain for at least one minor release before removal in a major version.