skills.rest
BitYoungjae
BitYoungjaeCOMMUNITY
Explore all skills by this author →
GitHub

chalkak-ocr-models-release

Update PKGBUILD and .SRCINFO to release chalkak-ocr-models to AUR.

42|1|Updated Feb 14, 2026
Search Tags:#automation#workflow#packaging#checksum#pkgbuild#aur
One-click install
npx skills add https://github.com/BitYoungjae/ChalKak --skill chalkak-ocr-models-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chalkak-ocr-models-release
Source: https://github.com/BitYoungjae/ChalKak/tree/main/.claude/skills/chalkak-ocr-models-release
Command: npx skills add https://github.com/BitYoungjae/ChalKak --skill chalkak-ocr-models-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction of releasing updated chalkak-ocr-models to the Arch User Repository (AUR) by handling version bumps, checksum refreshes, and metadata synchronization to ensure packaging accuracy.

Core Features & Use Cases

  • Safe sequence for source validation, checksum refresh, and AUR sync.
  • Guardrails to modify only PKGBUILD and .SRCINFO, preventing accidental changes to app code.
  • Use Case: Publishing new OCR model versions to the AUR and keeping metadata in sync with releases.

Quick Start

Run chalkak-ocr-models-release with a version argument to publish OCR model updates to AUR.

Frequently Asked Questions about chalkak-ocr-models-release

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

FAQPage Schema
How do I automate PKGBUILD and .SRCINFO updates for AUR releases?▼

AUR release automation modifies only PKGBUILD and .SRCINFO, refreshes checksums via updpkgsums, regenerates .SRCINFO using makepkg, and pushes auditable packaging metadata commits.

What is the safest way to sync OCR model versions to the Arch User Repository?▼

Safe AUR version syncing validates GitHub release assets first, then restricts modifications to PKGBUILD and .SRCINFO only, ensuring clean auditable commits without touching application code.

How does updpkgsums and makepkg work together to regenerate AUR package metadata?▼

In AUR packaging, updpkgsums refreshes checksums in PKGBUILD, while makepkg regenerates the .SRCINFO file, together ensuring packaging metadata stays synchronized with the validated source assets.

Can I use this workflow to correct packaging metadata without altering app code?▼

Yes, you can correct AUR packaging metadata safely because built-in guardrails restrict file modifications exclusively to PKGBUILD and .SRCINFO, explicitly preventing any accidental changes to the underlying application code.

Why do I need to validate GitHub release assets before pushing an AUR package update?▼

Validating GitHub release assets before pushing an AUR package update ensures the source files exist and match expected versions, preventing broken checksums and failed builds when users install the OCR models.

Related Skills

Explore More Software Engineering Skills→
JansenAnalyticsJansenAnalytics
5

release-manager

Automate changelog generation, version bumps, and GitHub releases via CLI.

Community
Intermediate
BitYoungjaeBitYoungjae
42

chalkak-release

Coordinate GitHub releases and three AUR package updates in one run.

Community
Advanced
gfargogfargo

key-rotation

Rotate SSH keys, API keys, database passwords, and GitHub secrets across Strut VPS stacks.

Community
Advanced
SteveGJonesSteveGJones
41

release-plugin

Automate packaging of source files into per-plugin release directories using release-mapping.yaml.

Community
Advanced