local-ci

Executes repository-defined local qualification commands to produce candidate-bound READY_FOR_MERGE evidence.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/coferlandia/coferlandia-skills --skill local-ci-coferlandia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-ci
Source: https://github.com/coferlandia/coferlandia-skills/tree/main/skills/engineering/local-ci
Command: npx skills add https://github.com/coferlandia/coferlandia-skills --skill local-ci-coferlandia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It provides a deterministic local qualification stage for development candidates that already have durable READY_FOR_CI evidence, producing auditable READY_FOR_MERGE results without relying on GitHub-native CI. ## Core Features & Use Cases - Profile-driven qualification: Reads the target repository's .coferlandia/ci/profile.json, validates and fingerprints it, then executes the declared local.qualification_commands in order against the exact candidate SHA. - Candidate-bound evidence: Emits a durable READY_FOR_MERGE comment with strategy LOCAL, candidate/base SHAs, and profile fingerprint, and blocks with LOCAL_QUALIFICATION_BLOCKED when runtimes or services are missing. - Strict boundaries: Never falls back to GitHub-native CI, never merges, and forces full requalification when the candidate, base, or profile changes. - Use Case: A pull request marked READY_FOR_CI needs qualification on a machine with the required services; this skill runs the repository's own qualification commands locally and records verifiable evidence for the merge stage. ## Quick Start Ask the agent to run local CI qualification for the current pull request that already has READY_FOR_CI evidence.

Frequently Asked Questions about local-ci

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

FAQPage Schema
How do I run local CI qualification for a pull request candidate?▼

Ensure the candidate has durable READY_FOR_CI evidence and a valid .coferlandia/ci/profile.json, then invoke local-ci. It validates and fingerprints the profile, runs the declared local.qualification_commands in order, and records READY_FOR_MERGE evidence for the exact candidate SHA.

What is the difference between local-ci and GitHub-native CI?▼

local-ci implements only the LOCAL qualification strategy using repository-defined commands on a local execution surface. GitHub-native CI belongs to the separate Chat ci controller, and local-ci never runs it as a fallback or performs merges.

What happens when a required local service or runtime is missing?▼

The skill reports LOCAL_QUALIFICATION_BLOCKED and stops without switching to GitHub-native CI. The controlling authority must explicitly decide the next action after the environment issue is resolved.

Does a code fix during qualification require re-running local CI?▼

Yes. A material correction creates a new candidate, which requires fresh review and READY_FOR_CI evidence, then a complete new Local CI run for the new SHA. Old-SHA or old-profile evidence never authorizes merge.

When should local-ci not be activated?▼

Do not activate it for generic test commands, GitHub Actions diagnosis, explicit Chat ci invocations, merge or release tasks, or merely because a controller reached READY_FOR_CI without an explicit local qualification request.