Menu

Post image 1
Post image 2
1 / 2
0

I built a CLI that runs your CI locally and fixes failures with Claude Code

DEV Community·Robles.H.·28 days ago
#e8xnCD7Q
#opensource#cli#ai#devops#stitch#claude
Reading 0:00
15s threshold

I built a CLI that runs your CI locally and fixes failures with Claude Code Stitch is an open-source CLI that parses your existing GitLab CI / GitHub Actions / Bitbucket Pipelines config, runs the jobs locally in parallel, and when something fails, hands the error to Claude Code or Codex CLI to fix. Re-verifies, commits, pushes. No API keys. MIT. The loop I wanted to kill Every push to a branch triggers cloud CI. Cloud CI takes 8–15 minutes. When it fails (and ~30% of pushes fail something), I open the logs in a browser, fix locally, push again, wait another 12 minutes. On a normal day, that's 30–60 minutes of waiting. On a bad day with a flaky job, it's an afternoon. I tried the existing tools: act runs GitHub Actions locally, but only GitHub, and it stops at "failed." Gitar / Nx Cloud are SaaS platforms that intercept failures in remote CI. Each fix attempt = a remote CI cycle, and they want your pipelines on their platform. Dagger + AI runs locally but expects you to rewrite every pipeline in their SDK.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More