agentleFS
YehudaFrankelYehudaFrankel/clankbrain/.claude/skills/_archived_04-environments/SKILL.md

environment-check

Skill16 starsChanged 7 months agoMITView on GitHub

Use when switching environments, updating config values, or verifying URLs/settings. Triggers on "check environment", "switch to production", "update URLs", "check config", "is this prod-ready".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check any config constants file for values that differ between environments

    line 13
  2. Distinctive:

    If changes are needed: show exactly what to change and ask for confirmation before editing.

    line 27

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

Environment Check

  1. Identify the target environment — local, staging, or production?
  2. Scan for hardcoded environment-specific values:
    • Grep for localhost, 127.0.0.1, dev URLs, test credentials, debug flags
    • Check any config constants file for values that differ between environments
  3. Verify config separation:
    • Are environment-specific values in a dedicated config location (constants file, env vars, config file)?
    • Is there a clear process for switching environments without touching business logic?
  4. Pre-deploy checklist:
    • All localhost/dev URLs replaced or behind config
    • No debug logging or test credentials in production path
    • Dependencies match production environment
    • Any required env vars documented and set
  5. Report: "Environment: [local/staging/prod]. Issues found: [list or none]. Ready to deploy: [yes/no]."
  6. If changes are needed: show exactly what to change and ask for confirmation before editing.

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.