appspec(3)

📦 version 0.6.0, in opensuse-leap 16.0

💖 appspec(3) 💖

hey bestie!! welcome to the User Contributed Perl Documentation page for appspec(3) — manual name folded right in, cute and cozy, no cap 💅 This is your group-chat explainer for the appspec utility, and we’re gonna make it make sense. ✨

🌸 NAME 🌸

appspec — Utilities for spec files for App::Spec cli apps 🎀

🦋 ABSTRACT 🦋

literally no abstract text here — the original leaves this space blank, and we respect the silence 🫶

✨ DESCRIPTION ✨

okay so this script is a collection of tools for authors of App::Spec command line scripts. it’s giving “toolbox for spec-file girlies” and we love that for us 💖

# generate completion
% appspec completion --bash path/to/spec.yaml
# generate pod
% appspec pod path/to/spec.yaml
# validate your spec file
% appspec validate path/to/spec.yaml
# generate a new App::Spec app skeleton
% appspec new --class App::foo --name foo --with-subcommands

🌈 GLOBAL OPTIONS 🌈

  • --help, -h — Show command help (flag) 👑

💅 SUBCOMMANDS 💅

🎀 completion 🎀

appspec  completion [options] <spec_file>

Generate completion for a specified spec file. This command takes a spec file and outputs the corresponding shell script for tab completion. no cap, it’s the tab-completion fairy 🧚✨

Options

  • --name — name of the program (optional, override the value from the spec)
  • --zsh — for zsh (flag)
  • --bash — for bash (flag)

Parameters

  • spec_file * — Path to the spec file (use '-' for standard input) 📥

🦄 new 🦄

appspec  new [options] [<path>]

Create new app. This command creates a skeleton for a new app. It will create a directory for your app and write a skeleton spec file. it’s giving “new project, new me” energy 🔥

Example:

appspec new --name myprogram --class App::MyProgram App-MyProgram

Options

  • --name, -n * — The (file) name of the app
  • --class, -c * — The main class name for your app implementation
  • --overwrite, -o — Overwrite existing dist directory (flag)
  • --with-subcommands, -s — Create an app with subcommands (flag)

Parameters

  • path — Path to the distribution directory (default is 'Dist-Name' in current directory)

🐚 pod 🐚

appspec  pod <spec_file>

Generate pod. This command takes a spec file and outputs the generated pod documentation. docs girlies, rise 🫶📚

Parameters

  • spec_file * — Path to the spec file (use '-' for standard input)

🔥 validate 🔥

appspec  validate [options] <spec_file>

Validate spec file. This command takes a spec file and validates it against the current App::Spec schema. vibe check for your spec, fr fr ✅

Options

  • --color, -C — output colorized (flag)

Parameters

  • spec_file * — Path to the spec file (use '-' for standard input)

💬 help 💬

appspec  help <subcommands> [options]

Show command help. when in doubt, ask for help — iconic behavior 👑

Options

  • --all — (flag)

👑 _meta 👑

appspec  _meta <subcommands>

Information and utilities for this app. meta? in my manual page? it’s more likely than you think 💀✨

🌟 _meta completion 🌟

appspec _meta completion <subcommands>

Shell completion functions. completion-ception, but make it cute 🌀

_meta completion generate

appspec _meta completion generate [options]

Generate self completion. your app completing itself? main character energy 👑

Options

  • --name — name of the program (optional, override name in spec)
  • --zsh — for zsh (flag)
  • --bash — for bash (flag)

🌸 _meta pod 🌸

appspec _meta pod <subcommands>

Pod documentation. pod, but make it meta 🎀

_meta pod generate

appspec _meta pod generate

Generate self pod. the docs write themselves? not quite, but slay 💖

and that’s the whole page, bestie!! this was appspec(3) from the User Contributed Perl Documentation, shipped with perl v5.42.0, dated 2025-03-23. slay, hydrate, and may your specs always validate 💖✨🎀

📦 where this page comes from