| name | perl-release-dist-ini |
| description | Load when reading, editing, or debugging any dist.ini file — any Perl distribution, any plugin bundle (Author::GETTY, Author::ETHER, Author::KENTNL, etc.), checking version config, plugins, metadata, prereqs |
| user-invocable | false |
| allowed-tools | Read, Grep |
| model | sonnet |
Generic Dist::Zilla dist.ini reference — applies to any distribution regardless of author bundle.
For [@Author::GETTY]-specific conventions (next-version semantics, POD commands, bundle options), the perl-release-author-getty skill applies additionally.
When analyzing dist.ini:
Section Detection
[@Author::PLUGIN_BUNDLE]
[Some::Plugin]
Common dist.ini Sections
| Section | Purpose |
|---|
name | Distribution name |
author | CPAN author |
license | License type |
copyright_holder | Copyright owner |
copyright_year | Override year |
[@Bundle] | Plugin bundle |
[Plugin] | Individual plugin |
Plugin Loading Order
[GatherDir] - Collects files
[PruneCruft] - Removes unwanted files
[Prereqs] / cpanfile - Dependencies
[Version plugins] - PkgVersion, AutoVersion, etc.
[Meta plugins] - MetaJSON, MetaYAML
[Test plugins] - Tests
[Release plugins] - UploadToCPAN, etc.
[VCS plugins] - Git::Commit, Git::Tag, etc.
Key Questions
- Which plugin bundle is used?
- Are there custom plugins configured?
- Are prereqs in dist.ini or cpanfile?
- What release mechanism is configured?
- What is the version in dist.ini — and does the bundle auto-bump it post-release or is it manual?