alpine-aports-docs

What problem does it solve?

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.

Core Features & Use Cases

• APKBUILD maintainer workflow guidance: Covers required metadata (pkgname/pkgver/pkgrel/pkgdesc/url/arch/license), subpackages patterns, common options, and the expected function order for fetch→unpack→prepare→build→check→package.
• abuild and apk command reference: Provides the typical command flow for building, debugging, checksum updates, and dependency handling, plus where to find detailed apk packaging internals.
• aports contribution and commit policy: Includes repository structure expectations (testing/community/main) and strict commit message formatting for add/upgrade/rebuild/move/rename/remove.

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.

Quick Start

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.