perl-release-dist-ini

Analyzes Dist::Zilla dist.ini configuration files for Perl distributions and plugin bundles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reading and debugging a Dist::Zilla dist.ini file requires knowing dozens of plugin conventions, loading order, and bundle semantics. This Skill provides a structured reference so you can quickly interpret, edit, or troubleshoot any dist.ini configuration. ## Core Features & Use Cases - Section Detection: Distinguishes plugin bundles like [@Author::GETTY] from individual plugins like [GatherDir]. - Plugin Loading Order Reference: Explains the standard sequence from GatherDir through Prereqs, version plugins, meta plugins, tests, release, and VCS plugins. - Diagnostic Checklist: Guides analysis with key questions about bundles, custom plugins, prereq location, release mechanism, and version bumping behavior. - Use Case: When a Perl release fails or a version is not bumped as expected, load this Skill to systematically inspect the dist.ini and identify which plugin or bundle setting is responsible. ## Quick Start Analyze this dist.ini file and tell me which plugin bundle it uses, where prereqs are declared, and how versioning is handled.

Frequently Asked Questions about perl-release-dist-ini

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

FAQPage Schema
How do I read a Dist::Zilla dist.ini file?

A dist.ini file contains distribution metadata like name, author, and license, plus plugin sections. Lines like [@Bundle] load plugin bundles, while [Plugin] sections configure individual plugins such as GatherDir or Prereqs.

What is the plugin loading order in Dist::Zilla?

Plugins generally run in this order: GatherDir collects files, PruneCruft removes unwanted files, Prereqs or cpanfile declares dependencies, then version, meta, test, release, and finally VCS plugins like Git::Commit and Git::Tag.

What is the difference between a plugin bundle and an individual plugin in dist.ini?

A plugin bundle like [@Author::GETTY] loads a preconfigured set of plugins with one line, while an individual plugin section like [MetaJSON] configures a single plugin. Bundles simplify configuration but hide defaults you may need to override.

Should prereqs go in dist.ini or cpanfile for Perl distributions?

Both approaches work with Dist::Zilla. Prereqs can be declared directly in dist.ini via the [Prereqs] plugin, or kept in a separate cpanfile that the build reads. Check which one your distribution uses before editing dependencies.

Why is my dist.ini version not bumping after release?

Version behavior depends on the bundle and version plugins configured. Some bundles like Author::GETTY auto-bump the version post-release, while others require manual edits. Inspect which version plugin is active, such as PkgVersion or AutoVersion.