gir-add-module

Scaffold a new .gir module with metadata and an install.sh template.

Updated May 22, 2025
One-click install
npx skills add https://github.com/curtjen/.gir --skill gir-add-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gir-add-module
Source: https://github.com/curtjen/.gir/tree/main/skills/gir-add-module
Command: npx skills add https://github.com/curtjen/.gir --skill gir-add-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured scaffold for adding a new module to the .gir installer, reducing manual setup and ensuring consistent templates.

Core Features & Use Cases

  • Guided collection of module metadata (name, description, platforms, install commands, and dotfiles).
  • Generates a ready-to-run modules/<name>/install.sh template with MODULE_* variables and a bootstrap workflow.
  • Creates placeholder dotfiles under modules/<name> to support initial symlink testing.
  • Marks the script executable and prints a summary to verify the scaffold.
  • Use Case: onboarding a new tool or configuration into the .gir installer with minimal friction.

Quick Start

Run the builder to scaffold a new .gir module by answering the guided prompts.

Frequently Asked Questions about gir-add-module

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

FAQPage Schema
How do I scaffold a new module for a bash dotfiles installer?

To scaffold a bash dotfiles module, this builder collects required metadata and generates a ready-to-use install.sh template with executable scripts and placeholder dotfiles for initial symlink testing.

What is a module scaffold used for in a dotfiles installer?

A module scaffold provides a structured template for onboarding new tools or configurations into a dotfiles installer, ensuring consistent bootstrap workflows and reducing manual setup friction.

How do I generate a symlink plan for new dotfiles?

You can generate a symlink plan by providing module metadata through guided prompts, which creates placeholder dotfiles and MODULE_ variables to support initial symlink testing.

Can I use this scaffold to add configurations for specific operating systems?

Yes, you can add configurations for specific operating systems by defining them in the MODULE_PLATFORMS variable during the guided metadata collection process.

What is the best way to create an install.sh template for a new tool?

The best way to create an install.sh template is using a guided scaffold that automatically applies MODULE_* variables, marks the script executable, and prints a summary to verify the setup.