pipeline-lab-plugin

Automates end-to-end GitHub Actions workflows for lab plugins.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jmagar/plugin-templates --skill pipeline-lab-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-lab-plugin
Source: https://github.com/jmagar/plugin-templates/tree/main/skills/pipeline-lab-plugin
Command: npx skills add https://github.com/jmagar/plugin-templates --skill pipeline-lab-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and maintenance of a complete CI/CD pipeline for lab plugins, removing manual setup and drift between environments.

Core Features & Use Cases

  • Implements and updates all four canonical workflows (ci.yaml, publish-image.yaml, release-on-main.yaml) and integrates pre-commit/lefthook for local development.
  • Provides Justfile targets and guidance to mirror CI locally and manage secrets, registry interactions, and release workflows.
  • Audits existing pipelines for drift and aligns templates with language-specific tools and boilerplates (Python, Rust, TypeScript).

Quick Start

Provide the plugin name and language, then generate the four workflows, pre-commit config, and Justfile targets tailored to your repository.

Frequently Asked Questions about pipeline-lab-plugin

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

FAQPage Schema
How do I set up GitHub Actions CI/CD pipelines for lab plugins?

To set up GitHub Actions CI/CD pipelines for lab plugins, you provide the plugin name and language to generate canonical workflows like ci.yaml, publish-image.yaml, and release-on-main.yaml along with Justfile targets and pre-commit configurations.

What is the best way to audit an existing GitHub Actions workflow for template drift?

Auditing an existing GitHub Actions workflow for template drift involves comparing your current pipeline against canonical templates to identify misalignments in versioning, caching, and guard patterns, then aligning them with language-specific boilerplates.

Can I use pre-commit and lefthook together in my CI/CD pipeline?

Yes, you can use pre-commit and lefthook together in your CI/CD pipeline. The setup integrates both tools as local development gates that enforce versioning and linting, ensuring local checks mirror the remote GitHub Actions workflows.

Does this pipeline automation support Python, Rust, and TypeScript repositories?

Yes, this pipeline automation supports Python, Rust, and TypeScript repositories. It aligns CI/CD templates with language-specific tools and boilerplates, ensuring the generated workflows and Justfile targets match your repository's ecosystem.

Why do I need a Justfile for my GitHub Actions release workflow?

You need a Justfile for your GitHub Actions release workflow because it provides localized targets that mirror CI commands, allowing you to manage secrets, registry interactions, and release workflows locally before pushing changes to the remote pipeline.