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.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.