CI-debugger – Debug GitHub Actions locally with breakpoints
Breakpoints and interactive shell for GitHub Actions when act only gives you log dumps.
Interactive CI pipeline debugger. Step through GitHub Actions workflows locally with Docker.
gdb for CI pipelines — shell into failing steps locally instead of push-wait-read loops.
Backend developers debugging CI/CD pipelines
act · nektos/act
PipeStep parses your GitHub Actions YAML, spins up the right Docker container, and gives you a step-through debugger for your run: shell commands. You can:
- Pause before each step and inspect the container state - Shell into the running container mid-pipeline (press I) - Set breakpoints on specific steps (press B) - Retry failed steps or skip past others
It deliberately does not try to replicate the full GitHub Actions runtime — no secrets, no matrix builds, no uses: action execution. For full local workflow runs, use act. PipeStep is for when things break and you need to figure out why without pushing 10 more commits. Think of it as gdb for your CI pipeline rather than a local GitHub runner.
pip install pipestep (v0.1.2) · Python 3.11+ · MIT · Requires Docker
Would love feedback, especially from people who've hit the same pain point. Known limitations are documented in the README + have some issues in there that I'd love eyeballs on!
Breakpoints and interactive shell for GitHub Actions when act only gives you log dumps.
Step-level analytics pinpoint exactly which instruction kills onboarding conversion.
Unblocks agents from hanging on interactive CLIs; solves a real agent-runtime pain point.
Visualizes pointer movement in trees for your code, unlike Python Tutor.
AIMA algorithms come alive—174 interactive visualizations beat static textbook pages.
Execution anchors enable replay-from-step debugging for non-deterministic agent runs.