aur-guides

name	aur-guides
description	Master skill for AUR (Arch User Repository) package development. Dispatches to specialized sub-skills for creating PKGBUILDs, auditing packages, submitting to AUR, and more. Use when working with AUR packages, PKGBUILDs, makepkg, pacman, or any Arch Linux packaging task.
license	MIT

Skill: aur-guides

Purpose

Master dispatcher for AUR package development. Routes to the right sub-skill for your task.

When NOT to Use

• Official Arch packages (use Package Maintainer workflow)
• Non-Arch Linux distributions
• Flatpak/Snap/AppImage packaging

Quick Reference: Which Skill to Use

Task	Sub-skill
Create/edit PKGBUILD	aur-pkgbuild
Packaging standards & guidelines	aur-package-guidelines
Submit package to AUR	aur-submission
Audit/validate with namcap	aur-audit
Build process & makepkg config	aur-makepkg
VCS packages (-git, -svn, -hg)	aur-vcs-packages
Pacman usage & queries	aur-pacman
AUR helpers (yay, paru)	aur-helpers
Aurweb RPC interface (queries, metadata)	aur-rpc

Complete AUR Package Lifecycle

1. Plan requirements
2. Create PKGBUILD        → aur-pkgbuild
3. Verify guidelines       → aur-package-guidelines
4. Build & test            → aur-makepkg
5. Audit                   → aur-audit
6. Submit to AUR           → aur-submission
7. Maintain & update       → aur-submission

Workflow Examples

New package: aur-pkgbuild → aur-package-guidelines → aur-makepkg → aur-audit → aur-submission

Update existing: aur-pkgbuild → aur-makepkg → aur-audit → aur-submission

VCS package: aur-vcs-packages → aur-pkgbuild → aur-audit → aur-submission

Verify metadata / build helper: aur-rpc (search, info, metadata archives)

Build reproducible: aur-audit → makerepropkg (see aur-package-guidelines)

Key Resources

• Arch Wiki
• AUR
• PKGBUILD man page
• Arch package guidelines
• AUR submission guidelines
• Aurweb RPC interface
• AUR metadata archives announcement

Essential Commands

makepkg -s              # Build + install deps
makepkg -i              # Build + install package
namcap PKGBUILD         # Audit PKGBUILD
updpkgsums PKGBUILD     # Update checksums
makepkg --printsrcinfo > .SRCINFO  # Generate .SRCINFO
shellcheck --shell=bash --exclude=SC2034,SC2154,SC2164 PKGBUILD

Best Practices

1. HTTPS for all source URLs
2. List all direct dependencies (no transitive reliance)
3. b2 or sha512 checksums preferred
4. SPDX license identifiers (GPL-3.0-or-later, MIT, BSD-3-Clause)
5. Quote "$pkgdir" and "$srcdir" everywhere
6. Regenerate .SRCINFO before every push
7. Use :: syntax in source array for unique filenames
8. License PKGBUILD under 0BSD (ship a LICENSE file + REUSE.toml in the repo)
9. No new PKGBUILD variables/functions unless prefixed with _ (avoid conflicts with makepkg internals)
10. Do NOT use makepkg subroutines (error, msg, msg2, plain, warning) — use printf/echo
11. Avoid /usr/libexec/ — use /usr/lib/$pkgname/ instead
12. For git sources, use the tag object hash (git rev-parse "v$pkgver") — tag names can be force-pushed
13. Verify package metadata with the AUR RPC (aur-rpc) before assuming upstream state