Claude-skill-registry devops-dx

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/devops-dx" ~/.claude/skills/majiayu000-claude-skill-registry-devops-dx && rm -rf "$T"

manifest: skills/data/devops-dx/SKILL.md

DevOps DX Helper

Lightweight playbook for CI/Railway env hygiene. Examples use this repo's Beads prefix (bd-); swap for your repo.

Common Tasks

Set GitHub Actions variables (non-secret paths, stub fixtures):

gh variable set CLERK_TEST_JWKS_PATH --body "frontend/e2e-smoke/fixtures/clerk-test-jwks.json"

gh variable set CLERK_TEST_PRIVATE_KEY_PATH --body "frontend/e2e-smoke/fixtures/clerk-test-private.pem"

Set GitHub Actions secrets (API keys, tokens):

```
gh secret set ZAI_API_KEY <<<"…"
```
```
gh secret set OPENAI_API_KEY <<<"…"
```

Sync Railway → GitHub secrets (if already stored in Railway):
- ```
scripts/sync_env_to_github.sh <environment> [service]
```
  - Copies Railway env vars to GitHub repo secrets (keys sanitized for GH).

When CI Fails for Missing Env

Identify missing var from logs (e.g.,
```
CLERK_TEST_JWKS_PATH missing
```
).
Decide scope:
- CI-only → set via
```
gh variable/secret set
```
  .
- Runtime (Railway) → set in Railway dashboard or
```
railway variables set
```
  .
Re-run the affected workflow:
```
gh workflow run CI --ref master
```
.

Notes

Keep stub/test fixtures in GH Actions vars, not Railway.
Use Railway for production secrets; keep CI-only secrets separate.
For multi-repo, reuse this skill and adjust variable names/prefixes per repo.