deployment-pipeline

Trace Rivetr deployment pipeline stages and debug failures in src/engine/pipeline.rs.

4|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/KwaminaWhyte/rivetr --skill deployment-pipeline-kwaminawhyte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-pipeline
Source: https://github.com/KwaminaWhyte/rivetr/tree/main/.claude/skills/deployment-pipeline
Command: npx skills add https://github.com/KwaminaWhyte/rivetr --skill deployment-pipeline-kwaminawhyte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug and understand Rivetr's deployment pipeline to diagnose failures and optimize the engine deployment process.

Core Features & Use Cases

  • Trace pipeline stages (Pending → Cloning → Building → Starting → HealthCheck → Running) and identify breakpoints.
  • Inspect key files and logs (src/engine/pipeline.rs, data/rivetr.db) to reproduce issues and verify fixes.
  • Use for troubleshooting deployment failures, improving rollback handling, and guiding engine-code changes.

Quick Start

Run a targeted failure investigation by inspecting pipeline stages in src/engine/pipeline.rs and reviewing recent deployment logs.

Frequently Asked Questions about deployment-pipeline

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

FAQPage Schema
How do I debug a Rivetr deployment pipeline that fails during the build stage?

Trace the deployment pipeline in src/engine/pipeline.rs to identify breakpoints between Pending and Running, then inspect data/rivetr.db and deployment logs to reproduce issues and verify fixes.

What pipeline stages does Rivetr go through from Pending to Running?

Rivetr deployment pipeline stages flow from Pending to Cloning, then Building, Starting, HealthCheck, and finally Running. Inspect src/engine/pipeline.rs to trace these transitions and identify where failures occur.

Do I need access to database state and logs to troubleshoot Rivetr deployment failures?

Yes, troubleshooting Rivetr deployment failures requires access to data/rivetr.db for database state, deployment logs, and src/engine/pipeline.rs to reproduce issues and verify fixes across pipeline stages.

What's the best way to diagnose a Rivetr health check failure during deployment?

Diagnose a Rivetr health check failure by inspecting the HealthCheck stage transition in src/engine/pipeline.rs, then cross-referencing deployment logs and data/rivetr.db to reproduce and verify the issue.

Can I use this approach to improve rollback handling in Rivetr's engine code?

Yes, you can guide engine-code changes for rollback handling by reviewing each pipeline stage transition in src/engine/pipeline.rs and using logs with database state to verify the updated deployment process.