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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
A small rule set that catches the problems seen most often in real Dockerfiles, with line numbers.
python scripts/lint_dockerfile.py Dockerfile
| Rule | Meaning |
|---|---|
DF001 | base image uses latest or has no tag, so builds are not reproducible |
DF002 | no USER instruction, the container runs as root |
DF003 | ADD used where COPY is enough (ADD is only needed for archives and URLs) |
DF004 | apt-get install without --no-install-recommends |
DF005 | apt-get update without removing /var/lib/apt/lists in the same layer |
DF006 | a secret-looking name (password, token, secret, api key) is set with ENV or ARG |
DF007 | sudo is used inside the image |
DF008 | no HEALTHCHECK (informational) |
JSON with instructions (count) and findings, a list of {"line", "rule", "severity", "message"}.
Severity is warning or info. The exit code is 1 when there is at least one warning.
Fix DF006 first, a secret baked into an image layer is exposed to anyone who can pull the image. Then DF002
and DF001. Suggest multi-stage builds when the image installs compilers.
A missing file exits with code 2.
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.
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.
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.
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.