Local Ci
Run the same build, test, and infra steps as remote CI inside Docker on your laptop before you push.
Overview
local-ci is a plugin marketplace for the Ship phase that lets Claude Code drive Docker-based local CI/CD to validate builds, run isolated tests, and stand up infra without pushing to remote runners.
What is this marketplace?
- Runs CI/CD-style pipelines locally using Docker containers
- Validates builds in environments closer to production without remote push
- Executes tests in isolated containers to reduce host pollution
- Can spin up supporting infrastructure locally for integration checks
- Ships as local-ci plugin version 0.0.24 from MrPuls marketplace
- Marketplace lists 1 plugin: local-ci at version 0.0.24.
Community signal: 3 GitHub stars.
What problem does it solve?
Pushing to remote CI to discover a broken build or flaky test wastes time, credits, and context for solo builders who could have caught it locally.
Who is it for?
Solo and small teams who already use Docker and want a Claude-assisted local dry-run of CI before every push.
Skip if: Builders who rely entirely on managed hosted CI with no local Docker setup or who only need lint-on-save without pipeline parity.
What do I get? / Deliverables
After installing local-ci, you can mirror pipeline steps in Docker on your machine and fix failures before the remote pipeline runs.
- Local pipeline runs mirroring remote CI stages
- Isolated test execution results before git push
- Optional local infra stacks for integration-stage checks
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Local CI mirrors the ship phase gate where you prove artifacts pass pipelines without burning remote runner minutes or catching failures late. Testing is the primary shelf because the plugin emphasizes isolated test runs and build validation in containers before release.
How it compares
Local Docker CI runner plugin, not a cloud deployment marketplace or generic unit-test skill.
Common Questions / FAQ
Who is Local Ci for?
Developers shipping with Claude Code who run Docker locally and want pipeline parity before pushing to GitHub or other remote CI.
When should I use Local Ci?
Use it in the ship and testing window whenever you change build scripts, services, or test matrices and need isolated validation without a remote run.
How do I add Local Ci to my agent?
Add the MrPuls/Local Ci Claude marketplace plugin to Claude Code and point it at your repo pipeline config so the agent can trigger local Docker runs.