getty-perl-release-author-getty

Configure Dist::Zilla distributions using the @Author::GETTY bundle and its release conventions.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Getty/p5-alien-libssh --skill getty-perl-release-author-getty-getty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: getty-perl-release-author-getty
Source: https://github.com/Getty/p5-alien-libssh/tree/main/.claude/skills/getty-perl-release-author-getty
Command: npx skills add https://github.com/Getty/p5-alien-libssh --skill getty-perl-release-author-getty-getty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Perl distributions using the [@Author::GETTY] Dist::Zilla plugin bundle follow non-obvious conventions — a committed LICENSE file, next-version semantics, per-file $VERSION placement, and custom POD commands — that cause silent build failures or metadata mismatches when misunderstood. ## Core Features & Use Cases - Bundle Option Reference: Documents every @Author::GETTY toggle including no_cpan, xs_alien, alien_* options, docker_* options, and run hooks for release automation. - Versioning & Release Rules: Explains that dist.ini holds the NEXT release version, each file needs its own $VERSION, executables belong in bin/, and only a human runs dzil release. - POD Conventions: Defines inline commands like =attr, =method, =opt, and =synopsis that PodWeaver transforms into standard sections. - Use Case: When a dist.ini contains [@Author::GETTY], load this Skill to correctly add an Alien-wrapped C library dependency, fix a failing LicenseFile check, or prepare the Changes file before a CPAN release. ## Quick Start Load this Skill whenever a dist.ini contains [@Author::GETTY] and follow its conventions for versioning, LICENSE handling, and release preparation.

Frequently Asked Questions about getty-perl-release-author-getty

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

FAQPage Schema
How do I configure a Dist::Zilla dist.ini with the @Author::GETTY bundle?

Set name, author, license, and copyright_holder, then add feature toggles like no_cpan, xs_alien, or docker_image as needed. Dependencies go in cpanfile, not dist.ini, and copyright_year must be kept since all GETTY distributions use it.

Why does the @Author::GETTY build fail with 'no LICENSE in the distribution'?

The bundle's LicenseFile plugin requires a committed LICENSE file matching the dist's license and copyright holder. Run dzil genlicense and git add LICENSE — an untracked file fails identically because Git::GatherDir only sees tracked files.

Does the version in dist.ini show the currently released CPAN version?

No. The version in the repository is always the NEXT release version. Check CPAN or git tags for the released version, and never bump the version manually since dzil release handles it automatically.

How do I wrap a C library with Alien in a GETTY distribution?

Set alien_build = 1 for Alien::Build-based dists with an alienfile, or use alien_repo plus alien_pattern options for Alien::Base wrapping. For XS modules linking against an Alien, use xs_alien = Alien::Foo to auto-configure MakeMaker::Awesome.

Can the AI agent run dzil release to publish to CPAN?

No. Only a human maintainer runs dzil release because it uploads to CPAN, tags, and pushes irreversibly. The agent may prepare the release by tidying Changes and confirming the build, but never executes the release itself.