ci

Audit CI gate coverage across Lefthook, Dagger, and GitHub Actions.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill ci-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/ci
Command: npx skills add https://github.com/misty-step/volume --skill ci-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit CI gates and strengthen pipeline integrity by ensuring lint, typecheck, tests, and secrets gates contribute to a green, reliable build.

Core Features & Use Cases

  • Audit across Lefthook, Dagger, and GitHub Actions to identify gaps and misconfigurations.
  • Auto-heal minor gaps by applying safe fixes (lint/format, lockfile updates) while escalating major issues.
  • Use Case: teams needing consistent gate green without manual gate-by-gate tuning.

Quick Start

Run bun run setup and then bunx convex dev to start auditing your CI gates.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I audit CI gates across GitHub Actions, Lefthook, and Dagger?

To audit CI gates, this skill analyzes your pipeline configurations across GitHub Actions, Lefthook, and Dagger to identify coverage gaps in lint, typecheck, tests, and secrets. It enforces canonical gates via the command dagger check --source .

Can CI pipelines auto-heal failing lint or format checks without bypassing tests?

CI pipelines can auto-heal failing lint or format checks through bounded self-heal mechanisms that apply safe fixes like lockfile updates. The skill strictly escalates genuine test failures and refuses to lower thresholds or bypass checks.

What is the best way to maintain a strict quality floor in GitHub Actions?

The best way to maintain a strict quality floor is by auditing gate coverage across lint, typecheck, tests, and secrets. This skill refuses to lower thresholds or bypass checks, escalating only genuine failures to keep pipelines green.

Why does my CI pipeline keep failing despite having Lefthook and Dagger configured?

Your CI pipeline might keep failing due to misconfigurations or gaps in gate coverage across lint, typecheck, and tests. Auditing these gates identifies missing canonical checks and applies safe self-heals to minor issues while escalating major problems.

Do I need Bun and Convex to start auditing my CI gates?

You need Bun and Convex to start auditing your CI gates. The quick start process requires running bun run setup and then bunx convex dev to initialize the environment and begin identifying pipeline gaps.