Verified:GitHub

aif-ci

Generate CI/CD pipeline configurations for GitHub Actions and GitLab CI.

31|2|Updated Mar 21, 2026

Search Tags:#automation #testing #ci/cd #linting #github actions #pipeline #gitlab ci

One-click install

npx skills add https://github.com/letuhao/lore-weave --skill aif-ci-letuhao

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: aif-ci
Source: https://github.com/letuhao/lore-weave/tree/main/.cursor/skills/aif-ci
Command: npx skills add https://github.com/letuhao/lore-weave --skill aif-ci-letuhao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a CI/CD pipeline requires knowing your project's language, package manager, linters, test frameworks, and platform-specific best practices. This Skill analyzes a repository and generates production-grade GitHub Actions or GitLab CI configurations with linting, static analysis, tests, and security scanning tailored to what the project actually uses. ## Core Features & Use Cases - Three operating modes: generate a pipeline from scratch, enhance an incomplete existing config, or audit a full setup against best practices with severity-ranked recommendations. - Deep project detection: identifies language, version constraints, package manager and lock file, linters, static analyzers, test frameworks, coverage tools, security scanners, and required service containers across PHP, Node.js, Python, Go, Rust, and Java. - Platform-specific output: produces one-workflow-per-concern files for GitHub Actions (lint.yml, tests.yml, build.yml, security.yml) or a staged .gitlab-ci.yml with caching, DAG needs, and report integration. - Use Case: A developer with a PHP project using PHPStan, Rector, and PHPUnit asks to set up CI, and receives separate GitHub Actions workflows with a PHP version matrix, composer caching, concurrency groups, and a security audit job. ## Quick Start Ask the assistant to set up CI for this project using GitHub Actions with security scanning enabled.

Frequently Asked Questions about aif-ci

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

FAQPage Schema

How do I set up a GitHub Actions CI pipeline for my project?▼

Run the skill in generate mode and it scans your repository for language, package manager, linters, and test frameworks, then writes separate workflow files for lint, tests, build, and security. Each workflow includes caching, concurrency groups, and least-privilege permissions.

GitHub Actions vs GitLab CI for project pipelines?▼

GitHub Actions uses one workflow file per concern with separate triggers and status checks, while GitLab CI uses a single .gitlab-ci.yml with stages and DAG needs. The skill supports both and picks the platform from your arguments or existing config files.

Can it improve an existing CI configuration instead of creating one?▼

Yes. Enhance mode adds missing jobs such as static analysis or security scanning to an incomplete pipeline, while audit mode checks a full setup against best practices and reports issues ranked by severity before fixing them.

Which languages and tools does the CI generator support?▼

It supports PHP, Node.js/TypeScript, Python, Go, Rust, and Java. Detection covers tools like PHPStan, Rector, ESLint, Biome, Ruff, mypy, golangci-lint, clippy, PHPUnit, Jest, Vitest, pytest, and language-specific security auditors.

Does it handle tests that need databases like PostgreSQL or Redis?▼

Yes. The skill greps test directories for service dependencies such as postgres, mysql, redis, and mongo, then adds service containers with health checks to the test job using the correct syntax for GitHub Actions or GitLab CI.