Reference APKBUILD metadata, abuild workflows, and aports commit policies.
npx skills add https://github.com/wenerme/ai --skill alpine-aports-docs
Please help me install this Agent Skill. Skill: alpine-aports-docs Source: https://github.com/wenerme/ai/tree/main/skills/alpine-aports-docs Command: npx skills add https://github.com/wenerme/ai --skill alpine-aports-docs
This Skill solves the problem of uncertainty and inconsistency when maintaining Alpine Linux packages in aports by providing a single, practical reference for correct APKBUILD and abuild workflows.
Use case example: You are upgrading an existing a port and need to update pkgver/pkgrel, regenerate sha512sums, run abuild -r, and produce a correctly formatted commit message for community or main.
Ask the Skill to generate an upgrade plan for an Alpine a port (including which APKBUILD fields to change, when to run abuild checksum, and what commit message to use) for your target pkgname and new upstream version.
High-intent search queries and answers about installing and using this skill.
Writing an APKBUILD file for Alpine Linux packages requires specific metadata like pkgname, pkgver, pkgrel, and license, alongside a deterministic function order for fetch, unpack, prepare, build, check, and package.
Correct Alpine aports commit messages follow strict formatting rules based on the action type, such as add, upgrade, rebuild, move, rename, or remove, while adhering to the repository structure of testing, community, or main.
Updating checksums for an Alpine Linux aport involves modifying the pkgver and pkgrel fields in your APKBUILD, then executing abuild checksum to regenerate the required sha512sums before running the final build.
The expected abuild workflow for validating an APKBUILD follows a deterministic sequence of fetch, unpack, prepare, build, check, and package functions, utilizing abuild and apk commands to manage dependencies and execute builds.
You can use this reference to review APKBUILD subpackages patterns and common options, as it provides maintainer-focused guidance for ensuring accurate metadata and validating build configurations in Alpine aports.
Alpine Linux package builds frequently fail after version changes if sha512sums are not regenerated via abuild checksum, or if the deterministic function ordering in the APKBUILD is not correctly maintained.
burnt-labsInstall the xiond CLI across macOS and Linux distributions via package managers.
CalmKernelTRAutomate cross-distro package builds and validation for AUR, Alpine APK, and RPM.
harnessAdd an SLSA Verification step to Harness pipelines for provenance attestations.
FlukeSupakornPackage Tauri v2 apps for Linux into AppImage, Debian, RPM, Flatpak, Snap, and AUR formats.
