delivery-closeout

Apply delivery/1 contract outcomes to Linear issues and GitHub mirrors.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hack-ink/codexlab --skill delivery-closeout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-closeout
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/delivery-closeout
Command: npx skills add https://github.com/hack-ink/codexlab --skill delivery-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates delivery state synchronization by consuming a pushed anchor and a delivery/1 contract to align Linear and GitHub issues with the authoritative contract.

Core Features & Use Cases

  • Contract-driven synchronization: validates and applies the delivery/1 contract to Linear issues and their GitHub mirrors.
  • State mirroring: updates GitHub issues to reflect the authoritative Linear state and contract outcomes.
  • Guardrails: enforces anchor reachability, contract integrity, and safe mutation ordering to prevent partial updates.

Quick Start

Provide a pushed anchor and a valid delivery/1 contract to perform a closeout synchronization.

Frequently Asked Questions about delivery-closeout

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

FAQPage Schema
How do I sync Linear issues with GitHub mirrors automatically?

To sync Linear issues with GitHub mirrors automatically, you provide a pushed anchor and a valid delivery/1 contract, which the system validates to align state and apply authoritative outcomes across both platforms.

What is contract-driven delivery closeout in Linear and GitHub?

Contract-driven delivery closeout is the process of consuming a delivery/1 contract to enforce authoritative Linear outcomes, mutating internal issues and mirroring those final states to GitHub to ensure alignment.

Can I reopen or update status-only on GitHub issues using a Linear contract?

Yes, you can update GitHub issues using a Linear contract by setting delivery_mode to status-only or reopen, allowing the system to mutate Linear and mirror those specific state changes without a full closeout.

Do I need a valid delivery contract to synchronize Linear and GitHub issues?

Yes, you need a valid delivery/1 contract with optional Linear refs to synchronize issues, because the system uses this contract as the authoritative source to validate anchor reachability and safely order mutations.

What guardrails prevent partial updates during GitHub and Linear issue synchronization?

Guardrails preventing partial updates during synchronization include enforcing anchor reachability, validating contract integrity, and applying safe mutation ordering to ensure Linear and GitHub states remain consistent.