ci

Coordinate local and cloud CI workflows to validate, ship, and track Pulp PRs.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/danielraffel/pulp --skill ci-danielraffel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/danielraffel/pulp/tree/main/.agents/skills/ci
Command: npx skills add https://github.com/danielraffel/pulp --skill ci-danielraffel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates local and cloud CI for Pulp, ensuring code is validated, PRs are created, and merges happen only on green, reducing risk and manual toil.

Core Features & Use Cases

  • Centralized orchestration of local and cloud CI for Pulp development workflows.
  • Primary use with Shipyard to validate, ship, and merge PRs on green across platforms.
  • Supports preflight checks, version-bump gating, and automated release tagging to ensure consistent surface versions.

Quick Start

Push a branch to origin to start the ship workflow and merge on green.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I automate PR creation and merge on green for continuous integration?

Automating PR creation and merge on green involves coordinating local and cloud CI workflows to validate code, ship branches, and track PRs. This ensures merges happen only when all gating scripts and checks pass.

What is the best way to coordinate local and cloud CI workflows for safe shipping?

Coordinating local and cloud CI workflows for safe shipping requires centralized orchestration to enforce deterministic ship cycles, preflight checks, and automated release tagging across multiple targets.

How do I enforce version bumps and gating scripts before merging a PR?

Enforcing version bumps and gating scripts before merging a PR is handled by applying gating rules within the CI orchestration, ensuring consistent surface versions and deterministic ship cycles before code reaches main.

Does continuous integration with Shipyard support pushing to main and automated releases?

Continuous integration with Shipyard supports pushing to main and automated releases by applying preflight checks, version-bump gating, and automated release tagging to ensure deterministic ship cycles across platforms.

Can I run CI checks across multiple targets before merging a pull request?

Running CI checks across multiple targets before merging a pull request is supported by the orchestration workflow, validating code across platforms to ensure merges only happen on green.