agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/diff-environments/SKILL.md

diff-environments

Skill0 starsChanged 16 days agoMITView on GitHub

Diff declared environments against what you can observe. Use when the user asks for environment drift, env diff, config drift, or /diff-environments. Do not invent production values. Do not change any environment.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent prod values.

    line 19
  2. Very specific:

    Read AGENTS.md if present.

    line 40
  3. Very specific:

    Read observable config only (repo files, user-provided output).

    line 41
  4. Distinctive:

    No secret values in the table — names of vars only.

    line 44

≈ “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

Diff environments

Compare declared vs observed. This is not a deploy and not plan-rollback.

Do not invent prod values. Do not change an environment.

Is this the right skill?

SignalDo this instead
How promotion worksfill context/environments.md
Spoken rollbackplan-rollback
Pipeline jobsreview-pipeline

Required inputs

  • context/environments.md (if missing, stop and say to fill it)
  • Whatever config or status you can actually read (files, user paste). Do not guess live prod.

Human decisions (do not invent)

  • Whether a drift is allowed

Procedure

  1. Read AGENTS.md if present. Read context/environments.md.
  2. Read observable config only (repo files, user-provided output). Mark anything you did not see as not observed.
  3. Find the home: docs/ops/env-diff-YYYY-MM-DD.md.
  4. Open references/env-diff-template.md. Copy every heading. Write n/a when unused.
  5. No secret values in the table — names of vars only.

Output

  • Path: docs/ops/env-diff-YYYY-MM-DD.md
  • Template: references/env-diff-template.md

Quality bar

  • environments.md was read or the skill stopped
  • Unseen values are not observed, not invented
  • No secret values
  • Unused headings are n/a

Done

  1. Path
  2. Drift count + not-observed count
  3. Next skill: human; then implement-change if they want config alignment

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.

Check your setup, free