ci-and-releases

Name: ci-and-releases
Availability: InStock
Author: Arthur

Automate CI and release hygiene for Lean 4 projects using lake build and dependency updates.

1|Updated Nov 11, 2025

Search Tags:#build #release #toolchain #CI #lake

Ready to run

npx skills add https://github.com/Arthur742Ramos/ComputationalPathsLean --skill ci-and-releases

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-and-releases
Source: https://github.com/Arthur742Ramos/ComputationalPathsLean/tree/main/.claude/skills/ci-and-releases
Command: npx skills add https://github.com/Arthur742Ramos/ComputationalPathsLean --skill ci-and-releases

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable checklist for keeping the repo green on CI and preparing small “release-like” changes (toolchain bump, version bump, dependency updates).

Core Features & Use Cases

CI mental model: clean checkout + lake build
Local verification, version bump, toolchain bumps
Dependency update workflow with lake update
Release hygiene: minimal, safe, and documented changes

Quick Start

Run a clean build and verify the executable; then bump toolchain or version as needed and refresh dependencies.

Frequently Asked Questions about ci-and-releases

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

FAQPage Schema

How do I keep my Lean 4 project green on CI with Lake?▼

CI hygiene for Lean 4 projects using Lake requires a clean checkout, lake build, and treating warnings as failures. This Skill automates verification, version bumps, toolchain updates, and dependency pinning to maintain a release-ready repository aligned with your pinned manifests.

What's the workflow for bumping the Lean toolchain version?▼

Run a clean build locally to verify the executable, update lean-toolchain when needed, refresh dependencies with lake update, and document changes. This ensures the bump passes CI and keeps the repository green before pushing.

How do I automate dependency updates without breaking the build?▼

Use lake update to refresh dependencies, verify with a clean local build, treat warnings as failures, and pin versions to your manifest. This workflow prevents silent breakage and keeps CI passing across dependency changes.

Can I use this for version and release bumps in a Lean 4 project?▼

Yes. This Skill provides a repeatable checklist for version bumps, toolchain updates, and release-like changes. It ensures minimal, safe, and documented changes that stay aligned with CI requirements and maintain repository stability.

What do I need before running CI verification locally?▼

A clean checkout of your ComputationalPaths Lean 4 project, Lake installed for building, and lean-action CI configured. Local verification with lake build and warning-as-failure enforcement mirrors CI behavior before pushing changes.

Why treat warnings as failures in the build process?▼

Treating warnings as failures prevents technical debt from accumulating and catches issues early in CI. This discipline ensures code quality across toolchain and dependency updates, reducing the risk of silent regressions in release-ready changes.