Cohere Continuous Integration

Overview

Make the required CI path deterministic and secret-free while preserving a trusted lane that detects real SDK and API drift.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Required pull-request checks should mock the application provider port and make no Cohere network calls.
• Fork pull requests must never receive Cohere secrets.
• A trusted branch, schedule, or manual workflow may run one bounded live probe with explicit spend and timeout limits.
• Pin runtime, SDK, action, and lockfile versions so failures are reproducible.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Identify required checks, fork behavior, secret scopes, and the existing provider adapter.
2. Add offline request-mapping, response, stream, error, retry, and redaction fixtures.
3. Make the offline lane required and assert that no network fallback is possible.
4. Add a separate protected live job with concurrency control, one request, timeout, and model discovery.
5. Upload sanitized test metadata without prompts, credentials, or customer content.
6. Document who may trigger the live lane and how model/API drift is triaged.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Error Handling

Examples

Use this compact handoff shape to keep the selected scope, validation evidence, and operational result reviewable.

Input:

provider=github-actions; required=offline; live=protected-main; max-requests=1

Expected handoff:

offline=required-pass; fork-secrets=none; live=bounded; artifacts=redacted

Resources

• Skill-specific official documentation
• TypeScript SDK
• Rate limits