devops-dx

Automates GitHub Actions and Railway variable/secret management with Bash tooling and CI failure diagnostics.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stars-end/agent-skills --skill devops-dx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-dx
Source: https://github.com/stars-end/agent-skills/tree/main/devops-dx
Command: npx skills add https://github.com/stars-end/agent-skills --skill devops-dx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires GitHub CLI, Railway CLI, and includes scripts (resource) components.

What problem does it solve?

Managing environment variables and secrets across GitHub Actions and deployment platforms like Railway can be a manual, error-prone process, leading to CI failures and deployment headaches. This Skill simplifies your DevOps hygiene.

Core Features & Use Cases

  • GitHub Actions Variable/Secret Management: Easily set and audit variables and secrets directly from the command line, ensuring your CI/CD pipelines have the correct configurations.
  • Railway Environment Sync: Synchronize environment variables from Railway to GitHub secrets, ensuring consistency across your development and deployment environments.
  • CI Failure Diagnostics: Provides clear guidance when CI fails due to missing environment variables, helping you quickly identify and resolve issues.
  • Use Case: Your CI pipeline is failing because a CLERK_SECRET_KEY is missing. Use this Skill to quickly check if it's set in GitHub Actions, or sync it from your Railway project if it exists there.

Quick Start

Use the devops-dx skill to set the CLERK_TEST_JWKS_PATH GitHub Actions variable.

Frequently Asked Questions about devops-dx

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

FAQPage Schema
How do I manage GitHub Actions secrets and variables from the command line?

Set and audit GitHub Actions variables and secrets directly using command-line tools that integrate with gh CLI, eliminating manual configuration errors and ensuring your CI/CD pipelines have correct configurations without switching between interfaces.

Can I sync environment variables from Railway to GitHub Actions?

Yes, synchronize environment variables from Railway to GitHub secrets to maintain consistency across development and deployment environments, reducing manual duplication and configuration drift between platforms.

What should I do when CI fails due to missing environment variables?

Use diagnostics to identify missing environment variables causing CI failures, then set them in GitHub Actions or sync them from Railway, enabling rapid resolution without manual log inspection.

How do I keep secrets separate between CI and production environments?

Differentiate CI-only versus production secrets during management, ensuring sensitive credentials are scoped correctly and preventing accidental exposure of production data in CI workflows.

Do I need both GitHub CLI and Railway CLI to use this automation?

Yes, both GitHub CLI and Railway CLI are required dependencies to enable full automation across GitHub Actions variable and secret management plus Railway environment synchronization.