Local CI Reproduction

VerifiedCaution

Run locally the equivalent checks of a CI pipeline (cargo check, npm build, UI tests).

Sby Skills Guide Bot
DevOpsBeginner
7/25/2026
Claude Code
#ci#local-ci#cargo#smoke-test#monorepo

Recommended for

Automated summary

Re-runs locally the four checks from `.github/workflows/ci.yml` (cargo check, desktop build, smoke UI test, landing page check) and summarizes the outcome.

Strengths

  • Covers the whole CI chain in one go across a mixed Rust + TypeScript repository
  • Keeps going after a failing step and reports every step's result together
  • Handles the Linux vs. non-Linux split for the smoke UI test
  • Clear final report: error details per failed step, or an explicit all-pass message

Limitations

  • Commands and paths are hardcoded to this specific repo and not portable as-is
  • Does not guarantee exact parity with the GitHub workflow beyond the four listed steps
  • No dependency installation or caching behavior is described
When to use it

Use it before pushing or opening a PR to confirm locally what GitHub CI is going to run.

When not to use it

Skip it when you only need to compile one crate or run a single targeted test.

Security analysis

Caution
Quality score82/100

The skill only performs ordinary CI checks (cargo check, npm builds, smoke test scripts). It does not exfiltrate data, disable safety, or use obfuscated payloads. However, it executes project-local npm and bash scripts, so it carries normal execution risk from a potentially compromised repository.

Findings
  • •Runs repository-local scripts and build commands (cargo, npm, bash scripts/run_smoke_ui.sh) that could execute arbitrary code if the repository is untrusted.
  • •No allowed-tools are declared, but the skill expects command execution capabilities.
How this analysis is made

Examples

Avant un push
CIと同じチェックをローカルで全部流して、結果をまとめて教えて
Pre-push validation
Run the full CI-equivalent checks locally and report which steps passed or failed.
Debug d'un échec CI
ローカルのCI相当チェックを実行して、失敗したステップのエラー詳細を見せて

name: ci
description: CIローカル再現 (.github/workflows/ci.yml 相当のチェックを一括実行)

.github/workflows/ci.yml と同等のチェックをローカルで順次実行する。

手順:

  1. cargo check --workspace を実行
  2. cd apps/desktop && npm run build を実行 (tsc + vite)
  3. スモークUIテスト: Linux では cd apps/desktop && bash scripts/run_smoke_ui.sh、それ以外では cd apps/desktop && npm run test:smoke-ui を実行
  4. ランディングページ: cd apps/landing && npm run check:latest を実行

全4ステップの結果をまとめて報告:

  • 各ステップの成功/失敗
  • 失敗したステップがある場合はエラー詳細を表示
  • 全ステップ成功の場合は「CI相当チェック全パス」と報告

いずれかのステップが失敗しても残りは続行すること。

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 files

This 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.md

From the root of a test project, save the file as .skill-downloads/local-ci-reproduction-mrzxuokz/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-reproduction-mrzxuokz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/local-ci-reproduction-mrzxuokz/download' --output '.skill-downloads/local-ci-reproduction-mrzxuokz/SKILL.md.part' && mv '.skill-downloads/local-ci-reproduction-mrzxuokz/SKILL.md.part' '.skill-downloads/local-ci-reproduction-mrzxuokz/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-reproduction-mrzxuokz/SKILL.md' && test -s '.skill-downloads/local-ci-reproduction-mrzxuokz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ci' && cp -R '.skill-downloads/local-ci-reproduction-mrzxuokz' '.claude/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 installation
openskills install './.skill-downloads/local-ci-reproduction-mrzxuokz'

openskills read 'local-ci-reproduction-mrzxuokz'

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 sync

Manual 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-reproduction-mrzxuokz/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.

Related skills