What problem does it solve? Working on the Alien::Libgit2 Perl distribution requires knowing project-specific facts that are easy to get wrong: why the libgit2 1.9.3 minimum exists, how the system and share install paths differ, which CMake flags are load-bearing, and how the four-job CI matrix pins install types. This Skill supplies that context so changes to the alienfile, bundled tarball, or workflows stay consistent. ## Core Features & Use Cases - Distribution facts: Explains the two install paths (PkgConfig probe vs. bundled CMake share build), the logic-free Alien::Libgit2.pm, and the required CMake flag set (USE_SSH=ON, USE_HTTPS=OpenSSL, REGEX_BACKEND=builtin). - Version floor rationale: Documents that the 1.9.3 minimum is a bug gate for the libssh2 timeout hang (libgit2 PR #7165), not an API requirement, and why Debian's probe failure is intended behavior. - Upgrade and verification procedures: Provides the step-by-step process for upgrading the bundled libgit2 tarball and the commands to test both install paths (dzil test with ALIEN_INSTALL_TYPE forced to share and system). - Use Case: When bumping the bundled libgit2 to a new release, follow the documented checklist to update the tarball, alienfile start_url, CI workflow version strings, and Changes entry, then verify both install paths locally. ## Quick Start Ask the agent to walk through upgrading the bundled libgit2 tarball in Alien::Libgit2 and verifying both the system and share install paths.