ci

Configures GitHub Actions pull-request checks around one documented Verify command.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill ci-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/ci
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill ci-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up CI by hand often means guessing the stack, duplicating existing checks, or creating workflows that always pass. This Skill inspects the real project setup and creates one shared Verify command that runs identically locally and on GitHub pull requests. ## Core Features & Use Cases - Stack Detection: Reads manifests, lockfiles, runtime version files, and existing workflows to identify the real package manager, runtime, and default branch instead of assuming npm or Node.js. - Verify Command Definition: Combines only the typecheck, test, and build commands that actually exist into a single documented Verify command in AGENTS.md, never inventing placeholder tests. - Safe Workflow Creation: Creates .github/workflows/verify.yml only when the path is free, preserves existing CI, runs Verify locally as proof, and never pushes or changes remote rulesets. - Use Case: After onboarding a new project, ask the agent to set up CI; it detects a pnpm TypeScript project, adds a verify script, writes a minimal GitHub Actions workflow, and confirms it passes locally. ## Quick Start Ask the agent to set up automatic GitHub checks for this project using the ci skill.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I set up GitHub Actions CI for an existing project?▼

Run the ci skill, which inspects your manifests, lockfiles, and existing workflows, defines one Verify command from your real typecheck, test, and build scripts, and creates a minimal verify.yml workflow triggered on pull requests and pushes to the default branch.

How do I add pull-request checks without breaking existing CI?▼

The skill preserves existing workflows and never overwrites verify.yml silently. If an existing workflow already provides equivalent checks, it reports that no setup is needed, and any normalization requires your explicit approval first.

Does this CI setup work with pnpm, Cargo, or Make instead of npm?▼

Yes. The skill detects the package manager from lockfiles and uses native task runners for non-JavaScript stacks, such as make verify or cargo test && cargo build --locked, rather than assuming npm or Node.js.

Will the skill add tests or linting to my CI automatically?▼

No. It only includes typecheck, test, and build commands that already exist and are configured. It never installs a test runner, invents placeholder tests, or adds lint, coverage, security scans, or version matrices by default.

Can the skill push the workflow or make the check required on GitHub?▼

No. It never pushes, publishes, or changes remote rulesets. Making the check required is a separate GitHub ruleset decision you make after reviewing and pushing the workflow yourself.