init-ci

Initialize CI/CD pipelines with Nix, GitHub Actions, and Blacksmith runners.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justinmoon/configs --skill init-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-ci
Source: https://github.com/justinmoon/configs/tree/main/home/skills/init-ci
Command: npx skills add https://github.com/justinmoon/configs --skill init-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the setup of Continuous Integration and Continuous Deployment (CI/CD) pipelines for projects, leveraging Nix for reproducible builds and GitHub Actions for automation.

Core Features & Use Cases

  • Nix-based CI: Ensures consistent build environments across development and CI.
  • GitHub Actions Integration: Provides pre-configured workflows for pre-merge checks, post-merge deployments, and nightly tasks.
  • Justfile as Source of Truth: Centralizes CI logic within justfile recipes for clarity and maintainability.
  • Use Case: When starting a new project that requires automated testing, linting, and deployment, use this Skill to quickly establish a robust CI/CD pipeline.

Quick Start

Use the init-ci skill to set up GitHub Actions workflows for a project with a flake.nix file.

Frequently Asked Questions about init-ci

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

FAQPage Schema
How do I set up GitHub Actions CI/CD pipelines using Nix for reproducible builds?

This approach creates GitHub Actions workflows that delegate to justfile recipes executed within a Nix development shell, ensuring consistent build environments across development and CI.

What is the best way to manage CI logic across pre-merge checks, post-merge deployments, and nightly jobs?

The best way to manage CI logic is centralizing it within justfile recipes. This Skill configures GitHub Actions workflows to delegate to those recipes, providing pre-configured workflows for pre-merge checks, post-merge deployments, and nightly tasks.

Do I need a flake.nix file to bootstrap continuous integration with Nix and GitHub Actions?

Yes, you need a flake.nix file to use this Skill. The quick start specifies using it to set up GitHub Actions workflows for a project with a flake.nix file to establish a robust CI/CD pipeline.

Can I use Blacksmith runners with GitHub Actions and Nix for continuous integration?

Yes, you can use Blacksmith runners. This Skill initializes CI/CD pipelines specifically for projects using Nix, GitHub Actions, and Blacksmith runners to automate testing, linting, and deployment.

Why use justfile as the source of truth for GitHub Actions workflows instead of inline workflow logic?

Using justfile as the source of truth centralizes CI logic for clarity and maintainability. Instead of writing inline workflow logic, GitHub Actions workflows delegate to justfile recipes executed within a Nix development shell.

Does this CI/CD setup support both pre-merge checks and post-merge deployments?

Yes, this CI/CD setup supports pre-merge checks, post-merge deployments, and nightly jobs. It provides pre-configured GitHub Actions workflows that delegate to justfile recipes executed within a Nix development shell.