Runs a list of HTTP checks against a base URL from a JSON file and reports status codes, response time and body assertions. Use when the user asks whether an API is up, wants a smoke test after a deploy, or needs to verify that endpoints return what the docs promise.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
A tiny smoke test runner with no dependencies. It sends real HTTP requests, so only point it at services the user owns or has permission to test.
python scripts/check_api.py checks.json --base-url https://staging.example.com
The checks file is a JSON list:
[
{"name": "health", "method": "GET", "path": "/health", "expect_status": 200, "expect_body_contains": "ok"},
{"name": "create", "method": "POST", "path": "/items", "json": {"name": "demo"}, "expect_status": 201}
]
Optional fields: headers (object), json (request body), expect_status (default 200),
expect_body_contains (string) and timeout (seconds, default 10).
JSON with base_url, passed, failed and results. Each result has name, ok, status,
elapsed_ms and, when it failed, a reason. The exit code is 1 when any check fails.
Report failures first with the reason and status code. Mention slow endpoints (over one second). Do not retry failing POST requests automatically, they may create duplicates.
A missing checks file exits with code 2. Invalid JSON or a malformed check exits with code 3. Connection errors are reported as failed checks, not crashes.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Turns git log output into a grouped markdown changelog using conventional commit prefixes such as feat, fix and docs. Use when the user prepares a release, asks for release notes, or wants a summary of what changed between two tags.
日本語の概要は準備中です。原文の説明を表示しています。
Writes clear git commit messages in the conventional commits style from a diff or a description of the change. Use when the user asks for a commit message, wants to tidy up a message before pushing, or has staged changes and no wording yet.
日本語の概要は準備中です。原文の説明を表示しています。
Profiles a CSV file column by column, reporting inferred type, missing values, unique counts and min, max and mean for numeric columns. Use when the user hands over a CSV and asks what is in it, whether the data is clean, or what to check before analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Checks a Dockerfile for common problems such as unpinned base images, running as root, ADD instead of COPY, secrets in ENV or ARG and apt-get without cleanup. Use when the user asks to review, harden or slim down a Dockerfile.
日本語の概要は準備中です。原文の説明を表示しています。
Compares a .env file with its .env.example template and reports missing keys, undocumented extra keys, empty values and example files that contain real looking secrets. Use when the user asks why an app fails on startup with missing configuration, or wants to check environment files before committing.
日本語の概要は準備中です。原文の説明を表示しています。
Compares two JSON files structurally and lists added, removed and changed values with their full paths. Use when the user asks what changed between two API responses, config files, fixtures or package manifests.
日本語の概要は準備中です。原文の説明を表示しています。