build
Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks
Use when installing or repairing Claude Desktop or Claude Code MCP config, checking status, backing up config files, or fixing config drift in openrouter-mcp
Use when changing concurrency limits, quota rules, circuit breakers, cleanup behavior, or other high-risk resilience policies in the collective-intelligence paths
Use when handling API key setup, credential rotation or deletion, security-audit runs, shared-environment risk checks, or security-document hygiene in openrouter-mcp
Use when running tests, reproducing the repository's assurance gate locally, checking failures, or verifying coverage for openrouter-mcp
Use when the user asks to continue with additional tasks while keeping current work in progress, or needs parallel branch development, hotfix interruption handling, and review sandboxes without extra clones. Use when tasks involve `git worktree add/list/remove/prune/lock/repair`, resolving branch-in-use conflicts across worktrees, configuring per-worktree settings (`git config --worktree`, `extensions.worktreeConfig`), or writing scripts that must resolve worktree paths safely with `git rev-parse`.
| name | build |
| description | Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish. |
No compilation step exists. "Build" means passing all static quality gates.
python3 when invoking Python modules or pip.python3 is unavailable but python exists, use python as fallback..venv.Run all three in order. All must exit 0:
ruff check src/ tests/
black --check src/ tests/
isort --check-only src/ tests/
If command executables are not on PATH, run module form:
python3 -m ruff check src/ tests/
python3 -m black --check src/ tests/
python3 -m isort --check-only src/ tests/
ruff check src/ tests/ --fix
black src/ tests/
isort src/ tests/
Re-run check mode after fixing to confirm clean state.
mypy src/
Not CI-required but recommended for new code.
If tools are missing:
python3 -m pip install -r requirements-dev.txt
If this fails with an externally-managed-environment error:
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements-dev.txt
npm run build is intentionally a no-op in this project, so it is not a quality gate.git add ..test skill after build passes to confirm nothing broke.