new-cask

Create a Homebrew cask stub for a new dotnet-sdk version and run the auto_updater.

732|37|Updated Sep 9, 2019
One-click install
npx skills add https://github.com/isen-ng/homebrew-dotnet-sdk-versions --skill new-cask-isen-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-cask
Source: https://github.com/isen-ng/homebrew-dotnet-sdk-versions/tree/main/.aiskills/new-cask
Command: npx skills add https://github.com/isen-ng/homebrew-dotnet-sdk-versions --skill new-cask-isen-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a streamlined workflow to add a new Homebrew cask for a dotnet-sdk version, enabling teams to expand available SDKs quickly.

Core Features & Use Cases

  • Create a correctly named Cask stub under Casks/ for a new major.minor.feature combination.
  • Run the auto_updater script to fetch the latest patch release and populate the cask with verified version/sha values.
  • Validate the cask against Homebrew style checks and open a PR to merge.

Quick Start

Create a new cask stub file for dotnet-sdk MAJOR-MINOR-FEATURE under Casks and run the updater to fill in the details.

Frequently Asked Questions about new-cask

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

FAQPage Schema
How do I add a new Homebrew cask for a dotnet-sdk version?

To add a new Homebrew cask, create a correctly named stub file under Casks/ following the major.minor.feature naming convention, then run the auto_updater to populate it with the latest patch release and verify it with style checks.

What is a Homebrew cask stub and how does the updater populate it?

A Homebrew cask stub is a template file using placeholder version and sha256 values. The auto_updater script fetches the latest patch release to replace those placeholders with verified version and sha256 checksums.

Can I run Homebrew style checks on a newly created dotnet-sdk cask?

Yes, the process validates the newly created cask file against Homebrew style checks to ensure it meets repository standards before opening a pull request to merge the dotnet-sdk version.

Do I need to manually find the sha256 checksum when creating a Homebrew cask?

No, you do not need to manually find the sha256 checksum. You create a cask stub with placeholder values, and the auto_updater automatically fetches and populates the verified sha256 checksum for the latest patch release.

What is the correct file naming convention for a dotnet-sdk Homebrew cask?

The correct naming convention for a dotnet-sdk Homebrew cask follows the major.minor.feature format, ensuring the file is correctly named under the Casks/ directory in the homebrew-dotnet-sdk-versions repository.