Patsship useful building blocks

Create a Pat, release it from your own repository, and help the Kirn ecosystem discover it.

Start the guide

Fork workflow

①

Create in your repo

Use Kirn's Pat scaffold so your source, metadata, tests, and release workflow stay together.

Create a Pat

②

Release from GitHub

Push your Pat, create a v* tag, and let the generated workflow build release artifacts.

Validate and release

③

Propose changes clearly

Fork this registry, make a focused branch, and open a pull request with useful evidence.

Open a pull request

Important: the pats repository is an index and contribution hub. Do not hand-edit registry.toml to add a Pat; the registry is populated through the release and maintainer workflow described below.

The complete path

Start with Start here for prerequisites, or jump directly to the fork and clone workflow.

What you will need

Git and a GitHub account.
A working Kirn toolchain.
Permission to push to your fork.
A Pat with a clear name, README, license, and runnable tests.