agentleFS
Lethe044Lethe044/agentskill-kit/skills/docker-compose-reviewer/SKILL.md

docker-compose-reviewer

Skill50 starsChanged 21 days agoMITView on GitHub

Reviews a docker-compose.yml for risky or fragile settings such as unpinned images, privileged containers, secrets in environment values, a mounted Docker socket and host networking. Use when the user asks to check, harden or clean up a compose file before deploying a stack.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat DC002 and DC005 as requiring a written reason, not a quick fix.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docker Compose reviewer

A line based review of a compose file. It needs no YAML library and no Docker installation.

When to use

  • The user asks for a review of docker-compose.yml or compose.yaml.
  • A stack is about to move from a laptop to a server.
  • A compose file contains passwords or tokens and the user is unsure whether that is a problem.

How to run

python scripts/review_compose.py docker-compose.yml

Rules

RuleLevelMeaning
DC001warningimage has no tag or uses latest
DC002warningprivileged: true gives the container almost full host access
DC003warninga secret-looking variable (password, token, secret, API key) has a literal value
DC004infoa port is published on all interfaces
DC005warningthe Docker socket is mounted, which gives the container control over the host
DC006infono restart policy
DC007infono healthcheck
DC008warningnetwork_mode: host removes network isolation

Output

JSON with services (count) and findings, a list of {"service", "line", "rule", "severity", "message"}. The exit code is 1 when there is at least one warning.

After running

  1. Fix DC003 first. Move secrets to an .env file that is not committed, or to Docker secrets, and reference them as ${NAME}.
  2. Pin images to a version. Use a digest (image@sha256:...) for production.
  3. Bind local-only services to 127.0.0.1:PORT:PORT.
  4. Treat DC002 and DC005 as requiring a written reason, not a quick fix.

Limits

The parser reads the common layout (services at two spaces, keys at four). Anchors, merge keys and extends are not followed.

Errors

A missing file exits with code 2.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.