coferlandia-ci-adapter

Adapts repositories to Coferlandia CI profiles, remote Development validation, and GitHub-native release publication workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Repositories need explicit, deterministic contracts before generic Chat/Local CI controllers, remote Development validation, or GitHub-native release publication can operate safely. This Skill studies a repository's real validation, CI, and release setup and materializes only the approved interface files, without inventing project commands or granting unintended authority. ## Core Features & Use Cases - CI Qualification Profile Generation: Validates, fingerprints (SHA-256), drift-checks, and atomically renders .coferlandia/ci/profile.json consumed by both Chat CI and Local CI. - Remote Development Validation: Materializes .coferlandia/development/validation.json plus a Draft-PR GitHub Actions workflow bound to the exact pull-request head SHA, with optional declarative toolchain setup actions. - GitHub-Native Release Publication: Renders an opt-in issue-comment publication workflow that delegates exact Commit-to-Release mechanics to coferlandia-release-publisher with actor authorization and merged-PR binding. - Use Case: A team wants Chat Coder to validate Draft PRs remotely. The adapter studies the repo's docs and workflows, proposes a Development contract with scoped commands and runner labels, and renders the fingerprinted contract and workflow after approval. ## Quick Start Ask the agent to adapt your repository for Coferlandia CI by studying its validation setup and rendering the approved CI profile, Development validation contract, or publication workflow.

Frequently Asked Questions about coferlandia-ci-adapter

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

FAQPage Schema
How do I adapt a repository for Coferlandia CI validation?▼

Run the adapter's repository study to inspect docs, scripts, and workflows, then use the CLI's profile validate, fingerprint, and render commands to produce `.coferlandia/ci/profile.json`. Rendering is deterministic and supports dry-run before writing.

How do I set up remote Development validation for Draft PRs on GitHub?▼

Define a Development contract at `.coferlandia/development/validation.json` with ordered commands, runner labels, shell, and optional setup actions, then render it with the development render command. The generated workflow binds to the exact pull-request head SHA and grants candidate code only contents: read permission.

Does the adapter support self-hosted GitHub Actions runners?▼

Yes, both Development validation and release publication accept explicit repository-declared runner labels, including self-hosted label lists. Publication defaults to ubuntu-latest only when repository study confirms it is intentionally valid.

Can the CI adapter publish releases or merge pull requests?▼

No, the adapter only materializes configuration contracts and workflows. Publication mechanics belong to `coferlandia-release-publisher`, Development evidence never grants merge authority, and Qualification, Integration, and Publication remain separate contracts.

Why does the adapter reject secrets or environment values in contracts?▼

Contracts store only environment variable names, never values, and the validator rejects any secret-bearing keys such as tokens or passwords. This keeps fingerprinted contracts safe to commit while credentials remain outside the delivery configuration.