add-package

Detect build systems and generate Nix packaging expressions from project sources.

8|1|Updated Oct 21, 2015
One-click install
npx skills add https://github.com/iamruinous/nix-config --skill add-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-package
Source: https://github.com/iamruinous/nix-config/tree/main/.opencode/skills/add-package
Command: npx skills add https://github.com/iamruinous/nix-config --skill add-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a project from a URL or local path and automates the creation of a Nix package by detecting the build system and extracting essential metadata.

Core Features & Use Cases

  • Auto-detect Build System: identify common build ecosystems (Go, Rust, Python, Node.js, CMake/Makefile, MkDocs, and shell-based builds) by inspecting project files.
  • Package Scaffolding: generate default.nix, a README, and basic packaging metadata from the detected project for quick deployment.
  • Repository Integration: prepare an index-ready package descriptor and consistent metadata to streamline inclusion in a central packages repository.

Quick Start

Provide a project URL or local path to auto-generate a Nix packaging scaffold.

Frequently Asked Questions about add-package

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

FAQPage Schema
How do I generate a Nix package from a GitHub repository URL?

You can generate a Nix package by providing a GitHub URL, which the tool analyzes to detect the build system, extract metadata like name and version, and produce a default.nix file along with a README and updated packages index.

What build systems does automatic Nix packaging detection support?

Automatic Nix packaging detection supports Go, Rust, Python, Node.js, CMake, Makefile, MkDocs, and shell-based builds by inspecting source files and repository metadata to scaffold the correct packaging expression.

Can I create a Nix expression from a local project path instead of a URL?

Yes, you can create a Nix expression from a local project path; the tool operates on local directories alongside VCS URLs and archives to detect the build system and extract essential metadata for packaging.

What metadata is extracted when auto-creating Nix packages?

When auto-creating Nix packages, the tool extracts the project name, version, description, license, and dependencies from the source files to populate the generated default.nix and package descriptor.

Does this Nix package generator work with Rust and Node.js projects?

Yes, this Nix package generator works with Rust and Node.js projects, supporting common ecosystems by inspecting project files to identify the build system and scaffold the appropriate packaging expression.

What files are generated when scaffolding a Nix package?

Scaffolding a Nix package generates a default.nix file containing the build expression, a README, and an index-ready package descriptor to streamline inclusion in a central packages repository.