How do I install the CI Local Guide skill?

Run npx skillmds@latest add jnzader-vault/ci-local-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI Local Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI Local Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI Local Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI Local Guide?

jnzader-vault (@jnzader-vault) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI Local Guide by jnzader-vault — Agent Skill

Name: CI Local Guide
Author: jnzader-vault

File contents

CI-Local Guide

Run your CI/CD pipeline locally before pushing to avoid broken builds in GitHub Actions.

Quick Commands

Check Stack Detection

./.ci-local/ci-local.sh detect   # Linux/Mac
.\.ci-local\ci-local.ps1 detect  # Windows

Quick Validation (pre-commit level)

./.ci-local/ci-local.sh quick    # Lint + compile

Full CI Simulation (pre-push level)

./.ci-local/ci-local.sh full     # Complete CI in Docker

Debug Mode (interactive shell)

./.ci-local/ci-local.sh shell    # Opens bash in CI container

Supported Stacks

Stack	Detection	Lint Command	Test Command
Java/Gradle	`build.gradle(.kts)`	`./gradlew spotlessCheck`	`./gradlew test`
Java/Maven	`pom.xml`	`./mvnw spotless:check`	`./mvnw test`
Go	`go.mod`	`golangci-lint run`	`go test ./...`
Rust	`Cargo.toml`	`cargo clippy`	`cargo test`
Node.js	`package.json`	`npm run lint`	`npm test`
Python	`pyproject.toml`	`ruff check .`	`pytest`

Git Hooks

CI-Local installs these hooks automatically:

Hook	Trigger	Checks
`pre-commit`	`git commit`	AI attribution, lint, security (Semgrep)
`commit-msg`	After message	No AI attribution in message
`pre-push`	`git push`	Full CI in Docker container

Bypass Hooks (Emergency Only)

git commit --no-verify  # Skip pre-commit
git push --no-verify    # Skip pre-push

Warning: Only use when absolutely necessary. You risk breaking CI.

Troubleshooting

"Docker not running"

Start Docker Desktop or run docker info to verify.

"Tests pass locally but fail in pre-push"

That's the point! The pre-push uses Docker to replicate the exact CI environment. Debug with:

./.ci-local/ci-local.sh shell
# You're now in the same environment as CI

"Hook blocked my commit"

Check the error message. Common causes:

AI attribution detected (remove Co-authored-by: Claude etc.)
Lint errors (run ./gradlew spotlessApply)
Security issues (check Semgrep output)

Configuration

Add Custom Semgrep Rules

Edit .ci-local/semgrep.yml:

rules:
  - id: my-custom-rule
    pattern: $DANGER_PATTERN
    message: "Dangerous pattern detected"
    severity: ERROR

Modify CI Commands

Edit the detect_stack() function in:

.ci-local/ci-local.sh (Linux/Mac)
.ci-local/ci-local.ps1 (Windows)

Philosophy

"If it passes locally, it MUST pass in CI."

CI-Local ensures:

Same JDK/runtime version as CI
Same Docker image as GitHub Actions
No "works on my machine" syndrome
Fast feedback loop before push

---name: ci-local-guidedescription: Guide for using CI-Local to run CI/CD locally before pushing. Trigger: run tests locally, CI simulation, pre-push validation, debugging CI failures, Docker CI---# CI-Local GuideRun your CI/CD pipeline locally before pushing to avoid broken builds in GitHub Actions.## Quick Commands### Check Stack Detection```bash./.ci-local/ci-local.sh detect # Linux/Mac.\.ci-local\ci-local.ps1 detect # Windows```### Quick Validation (pre-commit level)```bash./.ci-local/ci-local.sh quick # Lint + compile```### Full CI Simulation (pre-push level)```bash./.ci-local/ci-local.sh full # Complete CI in Docker```### Debug Mode (interactive shell)```bash./.ci-local/ci-local.sh shell # Opens bash in CI container```## Supported Stacks| Stack | Detection | Lint Command | Test Command ||-------|-----------|--------------|--------------|| Java/Gradle | `build.gradle(.kts)` | `./gradlew spotlessCheck` | `./gradlew test` || Java/Maven | `pom.xml` | `./mvnw spotless:check` | `./mvnw test` || Go | `go.mod` | `golangci-lint run` | `go test ./...` || Rust | `Cargo.toml` | `cargo clippy` | `cargo test` || Node.js | `package.json` | `npm run lint` | `npm test` || Python | `pyproject.toml` | `ruff check .` | `pytest` |## Git HooksCI-Local installs these hooks automatically:| Hook | Trigger | Checks ||------|---------|--------|| `pre-commit` | `git commit` | AI attribution, lint, security (Semgrep) || `commit-msg` | After message | No AI attribution in message || `pre-push` | `git push` | Full CI in Docker container |## Bypass Hooks (Emergency Only)```bashgit commit --no-verify # Skip pre-commitgit push --no-verify # Skip pre-push```**Warning**: Only use when absolutely necessary. You risk breaking CI.## Troubleshooting### "Docker not running"Start Docker Desktop or run `docker info` to verify.### "Tests pass locally but fail in pre-push"That's the point! The pre-push uses Docker to replicate the exact CI environment.Debug with:```bash./.ci-local/ci-local.sh shell# You're now in the same environment as CI```### "Hook blocked my commit"Check the error message. Common causes:- AI attribution detected (remove `Co-authored-by: Claude` etc.)- Lint errors (run `./gradlew spotlessApply`)- Security issues (check Semgrep output)## Configuration### Add Custom Semgrep RulesEdit `.ci-local/semgrep.yml`:```yamlrules: - id: my-custom-rule pattern: $DANGER_PATTERN message: "Dangerous pattern detected" severity: ERROR```### Modify CI CommandsEdit the `detect_stack()` function in:- `.ci-local/ci-local.sh` (Linux/Mac)- `.ci-local/ci-local.ps1` (Windows)## Philosophy> "If it passes locally, it MUST pass in CI."CI-Local ensures:1. Same JDK/runtime version as CI2. Same Docker image as GitHub Actions3. No "works on my machine" syndrome4. Fast feedback loop before push

Frequently asked questions

CI Local Guide