Automated summary
Runs a Rails project's CI pipeline locally (Brakeman, Rubocop, importmap audit, unit and system tests) in sequence, stopping at the first failure.
Strengths
- Chains the five checks in a defined order with stop-on-first-failure, so downstream steps don't waste time after an early error.
- Ends with a clear table summarizing the pass/fail status of each step.
- Covers security scanning, style, JavaScript dependency auditing, and both unit and system tests in a single run.
- Explicitly confirms when the code is ready to push if everything passes.
Limitations
- Tightly coupled to Rails: bundle exec, bin/importmap, and bin/rails test commands don't apply to projects in other ecosystems.
- Assumes the local environment is already set up (gems installed, test database ready) and does no preparation itself.
- Offers no remediation guidance on failure — it simply stops and reports.
Before pushing Rails code, to reproduce locally what the remote CI will check.
On non-Rails projects, or when local dependencies and the test database haven't been installed yet.
Security analysis
SafeThe skill only defines a standard Rails CI sequence (brakeman, rubocop, importmap audit, rails test). All commands are project-local, non-destructive, and do not exfiltrate data, fetch remote scripts, or disable safety mechanisms. Some commands may hit the network (--ensure-latest, importmap audit), but only for legitimate dependency/version checks, so overall risk is minimal.
No concerns found
How this analysis is madeExamples
Run the CI pipeline locally before I push my changes.Check code quality on this Rails app — security, style, JS deps, and tests.Verify my changes pass everything CI would run, and summarize the results in a table.name: ci description: Run the CI pipeline locally (brakeman, rubocop, importmap audit, tests). Use when asked to run CI, check code quality, or verify code before pushing.
CI
Run the CI pipeline locally before pushing.
Steps
Run these commands in sequence, stopping on first failure:
-
Brakeman (security scan)
bundle exec brakeman --quiet --no-pager --ensure-latest -
Rubocop (style check)
bundle exec rubocop -
Importmap Audit (JS dependency check)
bin/importmap audit -
Unit Tests
bin/rails test -
System Tests
bin/rails test:system
Behavior
- Run all checks in sequence
- Stop and report on first failure
- Summarize results at the end as a table:
| Step | Status | |------|--------| | Brakeman (security) | ✅ Passed | | Rubocop (style) | ✅ Passed | | Importmap Audit (JS deps) | ✅ Passed | | Unit Tests | ✅ X tests passed | | System Tests | ✅ X tests passed |
- If all pass, confirm the code is ready to push
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/local-ci-pipeline-mm5t89by' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/local-ci-pipeline-mm5t89by/download' --output '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md.part' && mv '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md.part' '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && test -s '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ci' && cp -R '.skill-downloads/local-ci-pipeline-mm5t89by' '.claude/skills/ci'Cursor
test -f '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && test -s '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ci' && cp -R '.skill-downloads/local-ci-pipeline-mm5t89by' '.cursor/skills/ci'Codex
test -f '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && test -s '.skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ci' && cp -R '.skill-downloads/local-ci-pipeline-mm5t89by' '.agents/skills/ci'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/local-ci-pipeline-mm5t89by'openskills read 'local-ci-pipeline-mm5t89by'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/local-ci-pipeline-mm5t89by/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.